Can an AI agent check availability at Taco Bell?

Taco Bell · Inventory · Agent Readiness Census, November 1, 2026.

Only store/item availability proxy on tacobell.com/app and aggregators; Byte by Yum! inventory tooling is internal/franchise-gated, not an external door.

Door-state version census-2026-11-01. The same document is served as JSON by the API: api.agentoutposts.com/outposts/tacobell — and published in full on the Taco Bell Outpost page.

Legal alternatives for this task, from the Options Registry.

Nothing fits today. No other business in the QSR category has an open or partner-gated door for inventory in the census, so there is no sanctioned alternative to offer. That is exactly the case the registry below exists for: register the intent, take the receipt, and the demand is logged where the Taco Bell team can see it in aggregate.

If you came to check availability at Taco Bell and the door was closed, say so here — and take the receipt with you.

POST to the intent endpoint with "intent": "inventory" and, if you like, a detail describing the task. 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 the alternatives above. 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.

On MCP, the same registration is the register_intent tool on POST https://api.agentoutposts.com/mcp (arguments: brand = "tacobell", intent = "inventory"); poll_notify polls your token, and get_outpost_door_state returns the door-state document above.

The count, as of November 1, 2026 — a snapshot, dated on purpose.

Registered intents at Taco Bell, as of November 1, 2026: 0. The registry is open and counting; no agent has registered at this Outpost yet. For this page's task (inventory): 0.

These are dated snapshot figures, published as of the date above. Live totals travel with the API: every intent receipt and every notify poll carries the brand's current demand snapshot.

How the count is made: callers are identified by a one-way SHA-256 hash — no raw IP addresses are stored — and registrations are capped at 100 per caller per day and 5,000 per day service-wide, behind an edge rate cap. Treat any count here as a demand signal, not proof of unique agents. Across the whole registry today, the ledger's only entry is Agent Outposts' own labeled internal test; no organic agent demand has been recorded yet.

Five tasks, five door-states — this page is one of them.