Pizza Hut publishes no public API: Yum!'s Byte platform is gated to franchise, supplier and partner integrations internally. An agent's only usable route is human pizzahut.com/app ordering or the DoorDash listing, which carries menu, prices, ordering and delivery tracking.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Pizza Hut's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | AGGREGATOR ONLY | DoorDash — Parent Yum! Brands publishes no public developer API/portal - Byte by Yum! is gated to franchise/supplier/partner integrations (api-evangelist profile corroborates, no official portal found). Official menu is human pizzahut.com/app only, e.g. Personal Pan page says order via app or pizzahut.com. DoorDash listing shows full menu. | Source — www.doordash.com | 2026-11-01 |
| Prices | AGGREGATOR ONLY | DoorDash listing states prices set directly by merchant and may differ delivery vs pickup. No direct price API; official site notes prices vary by store. | Source — www.doordash.com | 2026-11-01 |
| Inventory | AGGREGATOR ONLY | DoorDash — No direct inventory API. Only availability is aggregator store open/accepting status and human store locator; Byte inventory is internal/franchise-gated, not a consumer agent door. | Source — www.doordash.com | 2026-11-01 |
| Ordering | AGGREGATOR ONLY | DoorDash — Official page directs ordering to pizzahut.com/app or phone - human channels only. DoorDash listing confirms browse and place order for delivery/pickup via aggregator. | Source — www.pizzahut.com | 2026-11-01 |
| Tracking | AGGREGATOR ONLY | DoorDash — Pizza Hut Delivery Tracker exists in official app (Google Play listing: Track your order with Pizza Hut Delivery Tracker) - human app only, no API. Aggregator orders trackable in DoorDash. | Source — www.pizzahut.com | 2026-11-01 |
Agent-native surfaces at Pizza Hut: official MCP server — none found; llms.txt — not verified; API catalog (RFC 9727) — not verified. Automated access: Terms prohibit automated systems sending more requests than a human (search engines excepted); robots.txt fetch failed and llms/api-catalog checks were rate-limited (429) (evidence).
One page per task an agent might attempt at Pizza Hut — 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 Pizza Hut menu? |
| Prices | AGGREGATOR ONLY | Can an AI agent check prices at Pizza Hut? |
| Inventory | AGGREGATOR ONLY | Can an AI agent check availability at Pizza Hut? |
| Ordering | AGGREGATOR ONLY | Can an AI agent order from Pizza Hut? |
| Tracking | AGGREGATOR ONLY | Can an AI agent track a Pizza Hut order? |
If you came to do something at Pizza Hut 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 Pizza Hut, 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 Pizza Hut 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 Pizza Hut'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 Pizza Hut 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 Pizza Hut. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.