Subway has no public API and no agent-native surface, and its restaurants are independently operated by franchisees. Externally it is reachable only via human subway.com/app ordering or via DoorDash and Uber Eats, which carry menus, ordering and tracking.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Subway's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | AGGREGATOR ONLY | DoorDash / Uber Eats — No developer portal/API found. Official Terms confirm site/app features incl. online ordering are human channels; DoorDash Subway stores show full menus with merchant-set prices. | Source — www.subway.com | 2026-11-01 |
| Prices | AGGREGATOR ONLY | DoorDash / Uber Eats — DoorDash Subway listings note prices higher on third-party delivery and refer to subway.com for info; no price API. | Source — www.subway.com | 2026-11-01 |
| Inventory | AGGREGATOR ONLY | DoorDash / Uber Eats — Only per-store availability proxy (franchisees independently operate restaurants, per official Terms); no inventory API. SubwayPOS inventory tooling is franchisee-internal. | Source — www.subway.com | 2026-11-01 |
| Ordering | AGGREGATOR ONLY | DoorDash / Uber Eats — Ordering via subway.com/app (human) or DoorDash/Uber Eats, both offering delivery and pickup for Subway in listings checked; no ordering API. | Source — www.subway.com | 2026-11-01 |
| Tracking | AGGREGATOR ONLY | DoorDash / Uber Eats — Tracking in Subway app/web or aggregator used; no tracking API found. | Source — www.subway.com | 2026-11-01 |
Agent-native surfaces at Subway: official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: robots.txt 200 with Crawl-delay 10, sitemaps, and disallows for menu/order/profile paths; llms.txt and api-catalog 404 (S3 NoSuchKey) (evidence).
One page per task an agent might attempt at Subway — 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 Subway menu? |
| Prices | AGGREGATOR ONLY | Can an AI agent check prices at Subway? |
| Inventory | AGGREGATOR ONLY | Can an AI agent check availability at Subway? |
| Ordering | AGGREGATOR ONLY | Can an AI agent order from Subway? |
| Tracking | AGGREGATOR ONLY | Can an AI agent track a Subway order? |
If you came to do something at Subway 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 Subway, 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 Subway 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 Subway'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 Subway 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 Subway. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.