Can an AI agent check prices at Dunkin'?

Short answer: not at Dunkin' directly — the only sanctioned route runs through the aggregators Dunkin' names. The verified door-state for this exact task, the legal alternatives, and the demand registry are on this page.

The Dunkin' Outpost · Task · Prices · Door-state verified November 1, 2026

The answer.

Dunkin' · Prices · Agent Readiness Census, November 1, 2026.

IntentStateThe open routeSourceVerified
Prices AGGREGATOR ONLY Grubhub, Uber Eats and DoorDash Source — www.dunkindonuts.com 2026-11-01

Aggregator listings carry prices; official delivery page warns 'Prices may be different than in store.' No direct price API found.

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

What an agent can do instead.

Legal alternatives for this task, from the Options Registry.

AlternativeDoorThe routeVerified
Peet's Coffee OPEN API Peet's UCP MCP (Shopify Universal Commerce Protocol) 2026-11-01

Alternatives are computed exactly as the API computes them: same category as Dunkin' (Coffee), census door open or partner-gated, Dunkin' itself excluded. No paid placement — the order is the census order.

Register intent.

If you came to check prices 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 to the intent endpoint with "intent": "prices" 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 Dunkin', 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 = "dunkin", intent = "prices"); poll_notify polls your token, and get_outpost_door_state returns the door-state document above.

Demand at this wall.

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

Registered intents at Dunkin', 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 (prices): 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.

The other tasks at Dunkin'.

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

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.