Chipotle publishes no API and says the quiet part in its terms: no scraping, no data mining. What an agent can legitimately use is the set of delivery partners Chipotle names itself. This Outpost publishes the verified door-state and registers the demand that hits the wall.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Chipotle's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — Chipotle's official contact and FAQ page names its delivery partners, and DoorDash's Chipotle stores show full menus. No developer portal or API was found. | Chipotle contact / FAQ | 2026-11-01 |
| Prices | AGGREGATOR ONLY | The aggregator menus, which are merchant-set, and the human order process — Chipotle's US terms state prices are made clear during ordering. No price API exists. | Chipotle contact / FAQ | 2026-11-01 |
| Inventory | AGGREGATOR ONLY | Store and item availability exist only as a proxy in chipotle.com, the app and the aggregators. No inventory API was found. | Chipotle contact / FAQ | 2026-11-01 |
| Ordering | AGGREGATOR ONLY | chipotle.com and the app, handled by Chipotle support, or the named partners — DoorDash, Uber Eats, Grubhub — directly. Human channels only; no ordering API. | Chipotle contact / FAQ | 2026-11-01 |
| Tracking | AGGREGATOR ONLY | The partner's platform — Chipotle's official page directs partner-order issues to the partner, and Chipotle-app delivery links to DoorDash tracking. No tracking API exists. | Chipotle contact / FAQ | 2026-11-01 |
Agent-native surfaces at Chipotle: official MCP server — none found; llms.txt — not verified (census fetches conflicted: one llms-like 200, repeat fetches 404); API catalog (RFC 9727) — none published (404). Automated access: restrictive — Chipotle's UK terms explicitly ban text and data mining and web scraping via robot, bot, spider or scraper, and the US site runs a bot challenge (Chipotle UK terms).
If you came to do something at Chipotle 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 Chipotle, 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 Chipotle with a task — a menu to read, an order to place, a delivery to track — and found no API, an anti-scraping posture, and a set of delivery partners. 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 Chipotle'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.
Agent Outposts is not affiliated with Chipotle. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.