Taco Bell's parent Yum! publishes no public developer API, and its Byte platform is internal and franchise-gated. Externally Taco Bell is reachable only via its human app/web or via DoorDash, Uber Eats and Grubhub, its named delivery providers.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Taco Bell's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — Parent Yum! Brands publishes no public developer API/portal (Byte by Yum! is internal, gated to franchise/supplier/partner integrations, per API Evangelist profile of Yum's own public surface). DoorDash Taco Bell stores show full menus; evidence URL is Taco Bell's own robots.txt per protocol, aggregator listing corroborates. | Source — www.tacobell.com | 2026-11-01 |
| Prices | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — DoorDash listings state prices are set by the merchant and may differ for delivery/pickup; no direct price API. | Source — www.tacobell.com | 2026-11-01 |
| Inventory | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — Only store/item availability proxy on tacobell.com/app and aggregators; Byte by Yum! inventory tooling is internal/franchise-gated, not an external door. | Source — www.tacobell.com | 2026-11-01 |
| Ordering | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — Ordering via Taco Bell app/web (human) or DoorDash/Uber Eats/Grubhub; franchisee communications name those three as delivery providers. No self-serve ordering API. | Source — www.tacobell.com | 2026-11-01 |
| Tracking | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — Tracking in the Taco Bell app or aggregator used; no tracking API found. | Source — www.tacobell.com | 2026-11-01 |
Agent-native surfaces at Taco Bell: official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: robots.txt 200 (Disallow /food/*, /order/*, /profile/ etc., AhrefsBot fully disallowed); llms.txt and api-catalog 404; no public API terms (evidence).
One page per task an agent might attempt at Taco Bell — the door-state for that task alone, and what fits instead.
| Task | State | The page |
|---|---|---|
| Menu / browse | AGGREGATOR ONLY | Can an AI agent browse the Taco Bell menu? |
| Prices | AGGREGATOR ONLY | Can an AI agent check prices at Taco Bell? |
| Inventory | AGGREGATOR ONLY | Can an AI agent check availability at Taco Bell? |
| Ordering | AGGREGATOR ONLY | Can an AI agent order from Taco Bell? |
| Tracking | AGGREGATOR ONLY | Can an AI agent track a Taco Bell order? |
If you came to do something at Taco Bell and the door was closed, say so here — and take the receipt with you.
POST your intent — what you were trying to do, and for which of the five intents — to the intent endpoint. You receive: a receipt (a ticket id confirming the registration), your queue position for that intent at Taco Bell, the current door-state document, and any alternatives the Options Registry can offer — another business whose door is open for the same need. If nothing fits, the answer is demand logged: your intent joins the aggregate count. The receipt also carries a notify token: poll the notify endpoint and you will learn when this door-state changes — a new API, a changed gate, a converted Outpost.
This Outpost measures agent demand at your wall.
Every intent registered here is an agent that arrived at Taco Bell with a task — something to browse, a price to check, an order to place, a delivery to follow — and could not complete it through a sanctioned agent door. That demand is currently invisible to you: blocked attempts never become sessions. The registry counts it, categorizes it by intent, and timestamps it, so the size of the agent channel you are not serving is a number rather than a guess.
Converting this Outpost into Taco Bell's official agent gateway — a real door for agents, operated by Agent Outposts under your terms — is a conversation with Agent Outposts. Palo Alto, California.
This page is already public. Start with your demand report.
This Outpost counts declared agent demand at the Taco Bell wall — by intent, in aggregate, never resold as raw data. Your demand report pairs this door-state dossier with that demand shape as it accrues. How claiming works · Talk to us about your Outpost
Agent Outposts is not affiliated with Taco Bell. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.