The most digital pizza chain in America has no public API and no agent-native surface at all. 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 Domino's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | AGGREGATOR ONLY | DoorDash / Uber Eats — the menu is browsable on both marketplaces. The official menu is human web and app only at dominos.com; no public developer portal or API was found. | Domino's menu | 2026-11-01 |
| Prices | AGGREGATOR ONLY | DoorDash / Uber Eats listings; prices are also shown on the official human menu and vary by location. No direct price API exists. | Domino's menu | 2026-11-01 |
| Inventory | AGGREGATOR ONLY | DoorDash. The only availability signal is a store accepting orders, or an item's availability on an aggregator listing; no real-time stock API is published. | Domino's menu | 2026-11-01 |
| Ordering | AGGREGATOR ONLY | DoorDash / Uber Eats marketplaces — orders placed there are fulfilled by Domino's drivers. Direct ordering is human web, app, and AnyWare only; there is no self-serve ordering API. | Domino's menu | 2026-11-01 |
| Tracking | AGGREGATOR ONLY | DoorDash — orders placed through aggregators are trackable in the aggregator apps. Domino's own Tracker is a human web and app surface with no API, so direct-order tracking remains human-only. | Domino's Tracker | 2026-11-01 |
Agent-native surfaces at Domino's: official MCP server — none found; llms.txt — none published (returned 404 on 2026-11-01); API catalog (RFC 9727) — none published (404). Automated access: Domino's terms of use prohibit automated systems that send more requests than a human can; its robots.txt is permissive except for /qr/ (terms of use).
If you came to do something at Domino's 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 Domino's, 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 Domino's with a task — a menu to read, an order to place, a pizza to track — and found that the only programmatic route runs through a competitor's marketplace. 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 Domino'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 Domino's. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.