Restaurant locator and footprint mapping
Taco Bellエンドポイントを使えば、「Restaurant locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Taco Bell's US public ordering data into structured JSON — restaurant locations with capability flags, national and store-scoped menus with price and calorie data together, per-item customization matrices, and full nutrition-facts panels. Credential-free.
Find Taco Bell restaurants, browse the menu with prices and calories, and get combo, customization, and nutrition detail as structured JSON.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
21
サンプル数
8
ライブカタログスナップショット
稼働エンドポイント
8
メソッド
GET
必須パラメータ
18
スキーマ参照
8
{
"platform": "Taco Bell",
"endpoint": "taco-bell-stores",
"method": "GET",
"path": "/taco-bell/stores",
"auth": "apiKey"
}ユースケース
Find Taco Bell restaurants, browse the menu with prices and calories, and get combo, customization, and nutrition detail as structured JSON.
Taco Bellエンドポイントを使えば、「Restaurant locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Taco Bellエンドポイントを使えば、「Menu and pricing monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Taco Bellエンドポイントを使えば、「Nutrition data for diet and health apps」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のTaco Bellエンドポイントカタログから取得しています（エンドポイント8件、ドキュメント化されたリクエストパラメータ21個、公開レスポンススキーマ8件）。DocsとPlaygroundが参照しているカタログと同じものです。
Taco Bellのエンドポイントは8件、8つのリクエストファミリーに分類されています（App Menu、Categories、Menuほか5件）。
これらのTaco Bellエンドポイントには21個のリクエストパラメータがドキュメント化されており、うち18個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
8件のTaco Bellエンドポイントのうち8件が実際のサンプルレスポンスを、8件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Taco Bellのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Taco Bellのエンドポイントは8個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/taco-bell/app-menu
/taco-bell/categories
/taco-bell/menu
/taco-bell/nutrition
/taco-bell/product
/taco-bell/store
エンドポイントカタログ
/taco-bell/storesReturns Taco Bell US restaurants near a latitude/longitude, ordered by distance. Each store carries its store number, full postal address with coordinates, phone, distance, open status, timezone, today's published opening and closing hours, and Taco Bell's own per-store capability flags (breakfast, drive-thru, delivery, mobile ordering, open late, pickup shelves, Live Mas Cafe, online). A coordinate with no Taco Bell nearby returns an empty list rather than an error.
MCPツール taco_bell_stores
/taco-bell/storeReturns one Taco Bell US restaurant by store number: address and coordinates, phone, open status, timezone, delivery and online-ordering state, Taco Bell's per-store capability flags, mobile-pickup status and geofencing radius. Where GET /taco-bell/stores gives only today's window for each nearby restaurant, this returns the full published week, Monday-first, and each day's dayparts. Dayparts matter for ordering: Taco Bell's menu availability is daypart-scoped, so breakfast items and Balance Of Day items are orderable in different windows of the same day. Store numbers come from GET /taco-bell/stores.
MCPツール taco_bell_store
/taco-bell/categoriesReturns Taco Bell's US menu categories -- 17 at time of writing, including tacos, burritos, quesadillas, nachos, bowls, breakfast, drinks, snacks-sweets, specialties, party-packs, vegetarian, boxes-and-combos and the value menus. Each entry's slug is the value GET /taco-bell/menu takes. A category flagged hidden_from_menu is one Taco Bell does not surface in its own navigation; it is still fetchable. Takes no parameters.
MCPツール taco_bell_categories
/taco-bell/menuReturns the items in one Taco Bell US menu category, each with its product code, name, price, calorie count, product and food type, image, and flags for whether it is customizable, has a meatless variant, and is currently available in store. Category slugs come from GET /taco-bell/categories, and the endpoint accepts either the bare slug (`tacos`) or the full path form (`/food/tacos`). Taco Bell is one of the few brands publishing both price and calories in the same payload.
MCPツール taco_bell_menu
/taco-bell/store-menuReturns one Taco Bell US restaurant's entire menu -- every category and item in one call, each with its price, calories, product and food type, image, and whether it is currently carried and displayed at THIS store. Where GET /taco-bell/menu returns one category's items from the national default catalog, this is store-scoped: some items are absent or hidden at some restaurants, and this is the only endpoint that shows that per store. Also returns the store's current happy-hour discount window, published nowhere else in this family. The response can be cached at the edge for up to 24 hours, so treat it as a recent snapshot of what the store carries rather than a live per-second signal; for a store's serving-time windows (breakfast vs. Balance Of Day, etc.) use GET /taco-bell/store instead. Store numbers come from GET /taco-bell/stores.
MCPツール taco_bell_store_menu
/taco-bell/app-menuReturns one Taco Bell US restaurant's complete app-ordering catalog by store number: every category, every individually orderable product, AND every combo (kind "bundle") it carries. This is the only endpoint in this family that publishes combos at all -- each one resolved down to its full slot composition (choices[], each with min/max selections and the product codes it defaults to when not customized), not just a name and price. Also returns the store's named ordering windows (dayparts) and, per item, which dayparts it is orderable in. Comes from a different, credential-free backend than every other endpoint in this family -- no cookie, session, or account is required. Store numbers come from GET /taco-bell/stores.
MCPツール taco_bell_app_menu
/taco-bell/productReturns one Taco Bell US menu item in full: product code, name, description, price, rounded and unrounded calorie counts, every published image rendition, and cross-sell/upsell references. The distinguishing part is `customizations` -- the option groups the item accepts (proteins, included ingredients, add-ons, sauces, shells, upgrades, and Supreme/Fresco add and remove sets), each option carrying its own calorie delta and add-on price. Calorie deltas can be negative, since the Fresco style replaces sauces. Slugs come from GET /taco-bell/menu, and both the bare slug and the full path form are accepted.
MCPツール taco_bell_product
/taco-bell/nutritionReturns the complete nutrition-facts panel for one Taco Bell US menu item -- fats (total, saturated, trans, poly- and monounsaturated), cholesterol, sodium, potassium, carbohydrates, fiber, sugars including added sugars, protein, and the vitamin and mineral figures -- plus serving size and weight and the item's declared allergens. Values are unrounded as published, in the panel's own units: grams for fats, carbohydrates and protein, milligrams for cholesterol, sodium, potassium, calcium, iron and caffeine, and micrograms for vitamin D. This goes well beyond the calorie count on /taco-bell/menu and /taco-bell/product, which is all the menu pages themselves carry. The full component-by-component ingredient statement is available via include_ingredients; it runs to several kilobytes per item, so it is off by default.
MCPツール taco_bell_nutrition
関連API
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
Taco Bellのスクレイピング方法
Crawlora's Taco Bell endpoints return normalized public Taco Bell US ordering data as JSON with one API key — no Taco Bell account required. Taco Bell is one of the few chains publishing both price and calories in the same payload.
Pass a latitude and longitude to /taco-bell/stores for nearby restaurants with capability flags (breakfast, drive-thru, delivery, Live Mas Cafe, and more), then pass a store_number to /taco-bell/store for the full published week of hours and dayparts — breakfast and Balance Of Day items are only orderable in specific windows.
Call /taco-bell/categories for the 17 US menu categories, then /taco-bell/menu for one category's items with price, calorie count, and availability, or /taco-bell/store-menu with a store_number for that specific restaurant's live catalog, since some items are hidden at some locations.
Pass a category and product slug to /taco-bell/product for the item's full customization matrix — proteins, add-ons, sauces, and Supreme/Fresco swaps — each option carrying its own calorie delta and add-on price.
Pass a store_number to /taco-bell/app-menu for that restaurant's full app-ordering catalog — every category, every individually orderable product, and every combo, each combo resolved down to its slot composition (choices[] with min/max selections and the product codes it ships with by default). It also returns the store's named ordering windows (dayparts) and which dayparts each item is orderable in. Leading zeros in store_number are significant; pass the value back exactly as /taco-bell/stores returned it.
Call /taco-bell/nutrition for the complete facts panel (fats, sodium, vitamins, and more, unrounded in the panel's own units) beyond the calorie count the menu pages show — set include_ingredients for the full component-by-component ingredient statement.
FAQ
Call /taco-bell/stores with a coordinate for nearby locations, /taco-bell/categories and /taco-bell/menu for the national menu with prices and calories, /taco-bell/store-menu for one restaurant's live catalog, /taco-bell/product for full customization detail, or /taco-bell/nutrition for the complete facts panel — all return structured JSON with one API key.
Yes — /taco-bell/menu, /taco-bell/store-menu, and /taco-bell/product all include price alongside calories, one of the few chains in this catalog publishing both in the same payload.
No. /taco-bell/menu returns the national default catalog; some items are absent or hidden at specific restaurants, which only /taco-bell/store-menu (scoped to a store_number) shows.
Yes — /taco-bell/app-menu is the only endpoint in this family that publishes combos, and it resolves each one down to its full slot composition (choices[] with min/max selections and default product codes) rather than just a name and price. It reads Taco Bell's own credential-free app-ordering backend, a different source from the gateway /taco-bell/stores and /taco-bell/store-menu use.
Yes — /taco-bell/product's customizations carry a calorie delta and add-on price per option (proteins, sauces, Fresco swaps); deltas can be negative, since Fresco style replaces higher-calorie sauces.