The Wendy's
Outpost.

Wendy's publishes no public API and no agent-native files, and its terms prohibit launching automated systems including robots and spiders. Wendy's itself names DoorDash, Grubhub, Postmates and Uber Eats as its official delivery partners, while direct web ordering is human-only.

Status · Collecting demand · Registry opened November 1, 2026

The doors, as assessed.

Five intents, checked against Wendy's public sources on November 1, 2026.

IntentStateThe open routeSourceVerified
Menu / browse AGGREGATOR ONLY DoorDash / Uber Eats / Grubhub — No developer portal/API found (only third-party scraped menu APIs). Official location page lists official third-party partners DoorDash, Grubhub, Postmates, Uber Eats and wendys.com/delivery. Source — locations.wendys.com 2026-11-01
Prices AGGREGATOR ONLY DoorDash / Uber Eats / Grubhub — Official page notes delivery prices may be higher than at restaurant; DoorDash Wendy's menus show merchant-set prices. No price API. Source — locations.wendys.com 2026-11-01
Inventory AGGREGATOR ONLY DoorDash / Uber Eats / Grubhub — Only availability proxy via store/aggregator menu availability; official page says delivery availability varies by location. No inventory API. Source — locations.wendys.com 2026-11-01
Ordering AGGREGATOR ONLY DoorDash / Uber Eats / Grubhub — Official page: start delivery in Wendy's app/wendys.com or via official partners DoorDash/Grubhub/Postmates/Uber Eats. Direct web ordering (order.wendys.com, incl. guest) is human-only. Source — locations.wendys.com 2026-11-01
Tracking AGGREGATOR ONLY DoorDash / Uber Eats / Grubhub — Tracking is in the Wendy's app or the aggregator used; no tracking API found. Source — locations.wendys.com 2026-11-01

Agent-native surfaces at Wendy's: official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: Wendy's terms prohibit launching automated systems incl. robots/spiders; robots.txt 200 (Allow / with Disallow for /api/, order/account paths); llms.txt and api-catalog 404 (evidence).

The five tasks, page by page.

One page per task an agent might attempt at Wendy's — the door-state for that task alone, and what fits instead.

TaskStateThe page
Menu / browse AGGREGATOR ONLY Can an AI agent browse the Wendy's menu?
Prices AGGREGATOR ONLY Can an AI agent check prices at Wendy's?
Inventory AGGREGATOR ONLY Can an AI agent check availability at Wendy's?
Ordering AGGREGATOR ONLY Can an AI agent order from Wendy's?
Tracking AGGREGATOR ONLY Can an AI agent track a Wendy's order?
Register intent.

If you came to do something at Wendy's and the door was closed, say so here — and take the receipt with you.

GET https://api.agentoutposts.com/outposts/wendys POST https://api.agentoutposts.com/outposts/wendys/intent GET https://api.agentoutposts.com/outposts/wendys/notify/{token}

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 Wendy'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.

For Wendy's teams.

This Outpost measures agent demand at your wall.

Every intent registered here is an agent that arrived at Wendy's 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 Wendy's'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.

On the Wendy's team?

This page is already public. Start with your demand report.

This Outpost counts declared agent demand at the Wendy's 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 Wendy's. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.