The Dunkin'
Outpost.

Dunkin' has no direct developer or agent-native door: its official delivery page says it has teamed up with Grubhub, Uber Eats and DoorDash, and all five intents are reachable only through those aggregators. First-party menu and Order Ahead remain human web/app only.

Status · Collecting demand · Registry opened November 1, 2026

The doors, as assessed.

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

IntentStateThe open routeSourceVerified
Menu / browse AGGREGATOR ONLY Grubhub, Uber Eats and DoorDash — Official delivery page says Dunkin' 'has teamed up with Grubhub, Uber Eats and DoorDash' and most favorites are available for delivery; the official menu at dunkindonuts.com/en/menu and Order Ahead in the Dunkin' app are human-only. No developer portal, MCP, llms.txt or api-catalog found. Source — www.dunkindonuts.com 2026-11-01
Prices AGGREGATOR ONLY Grubhub, Uber Eats and DoorDash — Aggregator listings carry prices; official delivery page warns 'Prices may be different than in store.' No direct price API found. Source — www.dunkindonuts.com 2026-11-01
Inventory AGGREGATOR ONLY Grubhub, Uber Eats and DoorDash — Official page instructs users to enter a delivery address on Grubhub.com, UberEats.com or DoorDash.com to see participating Dunkin' stores — that aggregator availability check is the only non-human inventory signal found. No direct inventory API. Source — www.dunkindonuts.com 2026-11-01
Ordering AGGREGATOR ONLY Grubhub, Uber Eats and DoorDash — Delivery ordering is exclusively via the three named aggregators per the official page; first-party Order Ahead is human mobile-app only. No ordering API found. Source — www.dunkindonuts.com 2026-11-01
Tracking AGGREGATOR ONLY Grubhub, Uber Eats and DoorDash — Delivery order tracking and problem reporting are handled by the aggregator: official page directs users to Grubhub, Uber Eats or DoorDash customer service on their respective sites/apps. No Dunkin' tracking API found. Source — www.dunkindonuts.com 2026-11-01

Agent-native surfaces at Dunkin': official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: Minimal/permissive: robots.txt is User-agent * with no Disallow rules (body shows 'undefined') plus a sitemap link; no AI-bot block seen (evidence).

The five tasks, page by page.

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

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

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

GET https://api.agentoutposts.com/outposts/dunkin POST https://api.agentoutposts.com/outposts/dunkin/intent GET https://api.agentoutposts.com/outposts/dunkin/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 Dunkin', 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 Dunkin' teams.

This Outpost measures agent demand at your wall.

Every intent registered here is an agent that arrived at Dunkin' 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 Dunkin' 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 Dunkin' team?

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

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