Store locator and footprint mapping
Dunkin'エンドポイントを使えば、「Store locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Dunkin's public store and menu data into structured JSON — a directory browse across all 44 US states Dunkin operates in, coordinate-based proximity search with distance and amenity labels, full per-store detail including active third-party delivery platforms, and the national menu catalog. Credential-free.
Browse Dunkin's store directory, find nearby stores by coordinate, and get the national menu and full store detail as structured JSON.
エンドポイントファミリー
4
ドキュメント化されたパラメータ
11
サンプル数
4
ライブカタログスナップショット
稼働エンドポイント
4
メソッド
GET
必須パラメータ
7
スキーマ参照
4
{
"platform": "Dunkin'",
"endpoint": "dunkin-nearby",
"method": "GET",
"path": "/dunkin/nearby",
"auth": "apiKey"
}ユースケース
Browse Dunkin's store directory, find nearby stores by coordinate, and get the national menu and full store detail as structured JSON.
Dunkin'エンドポイントを使えば、「Store locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Dunkin'エンドポイントを使えば、「Delivery-platform coverage research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Dunkin'エンドポイントを使えば、「Menu content monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Dunkin'エンドポイントを使えば、「Local retail presence monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のDunkin'エンドポイントカタログから取得しています（エンドポイント4件、ドキュメント化されたリクエストパラメータ11個、公開レスポンススキーマ4件）。DocsとPlaygroundが参照しているカタログと同じものです。
Dunkin'のエンドポイントは4件、4つのリクエストファミリーに分類されています（Directory、Menu、Nearbyほか1件）。
これらのDunkin'エンドポイントには11個のリクエストパラメータがドキュメント化されており、うち7個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
4件のDunkin'エンドポイントのうち4件が実際のサンプルレスポンスを、4件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Dunkin'のエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Dunkin'のエンドポイントは4個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/dunkin/directory
/dunkin/menu
/dunkin/nearby
/dunkin/store
エンドポイントカタログ
/dunkin/nearbyReturns Dunkin restaurants within a radius of a latitude/longitude, ordered nearest first, each with its distance in miles and kilometres, full address, phone, coordinates, the published week of hours, whether it's permanently closed, amenities, payment methods, pickup/delivery service types, which third-party delivery platforms are active, its Google Place id, timezone, and website/menu/order URLs. This is the proximity search the directory browse cannot do -- GET /dunkin/directory walks a state to city to store tree, which requires knowing the administrative path in advance. Each result carries the store id as `path`, which GET /dunkin/store also takes, so the two chain directly. `total_in_radius` reports how many stores fall inside the radius overall, which is usually far more than one page; use `offset` to walk it. A coordinate with no Dunkin nearby returns an empty list rather than an error.
MCPツール dunkin_nearby
/dunkin/directoryReturns one level of Dunkin's store directory tree. Omit path for the root, which lists every US state Dunkin operates in; pass a state's path (e.g. "ny") to list its cities, or a state/city path (e.g. "ny/new-york") to list its stores. Each child carries its name, path, URL and how many stores sit under that branch. A child with is_store true is a store rather than another directory level -- pass its path (a store id) to GET /dunkin/store. This is a directory browse, not a proximity search: use GET /dunkin/nearby for a radius lookup.
MCPツール dunkin_directory
/dunkin/storeReturns one Dunkin store: name, full postal address, phone, coordinates, opening hours for every day of the week, whether it's permanently closed, amenities (curbside pickup, drive-thru, wifi, kosher, turbo oven, K-Cup pods), Dunkin's own free-text feature labels, accepted payment methods, pickup/delivery service types, which third-party delivery platforms are active, the Google Place id, and the store's website/menu/order URLs. path is a store id -- from a /dunkin/directory child with is_store true, a /dunkin/nearby result's path, or the trailing digits of a dunkindonuts.com store URL. An unknown id returns a 404.
MCPツール dunkin_store
/dunkin/menuReturns Dunkin's national menu: item names, descriptions and photos grouped into categories (Iced Drinks, Hot Drinks, Frozen Drinks, Sandwiches & Wraps, Savory Bites, Donuts & Bakery, Snacks and Sides). Dunkin publishes one shared menu across every US store, so this takes no store parameter. Does not carry prices or nutrition -- pricing varies by market/franchisee and isn't part of this content.
MCPツール dunkin_menu
関連API
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Dunkin'のスクレイピング方法
Crawlora's Dunkin' endpoints return normalized public Dunkin' store and menu data as JSON with one API key — no Dunkin' account required. Dunkin' publishes one shared national menu (names, descriptions, and photos) but no price or nutrition data through this source.
Pass a latitude and longitude to /dunkin/nearby for stores within a radius, ordered nearest first, each with distance in miles and kilometres, the published week of hours, Dunkin's own amenity labels, and which third-party delivery platforms are active there.
Call /dunkin/directory with no path for the root — the 44 US states Dunkin operates in — then pass a child's path to descend from state to city to store, useful when you need to enumerate stores by administrative region rather than a coordinate.
Pass the path from either a /dunkin/nearby result or a /dunkin/directory entry flagged is_store to /dunkin/store for that location's name, address, phone, coordinates, hours, and feature labels — passing a directory path (not a store path) returns a 404 rather than a hollow record.
Call /dunkin/menu with no parameters for Dunkin's single shared menu across every US store — item names, descriptions, and photos grouped into categories. There's no price or nutrition data; see a /dunkin/store result's menu_url for a link to that specific store's own ordering page if pricing is needed.
/dunkin/nearby's total_in_radius reports how many stores fall inside the radius overall, usually more than one page — use offset to walk the full set for a dense metro area.
FAQ
Call /dunkin/nearby with a coordinate for nearby stores ordered by distance, /dunkin/directory to browse the state-to-city-to-store tree, /dunkin/store with a store path for full detail, or /dunkin/menu for the national menu — all return structured JSON with one API key.
Partially. /dunkin/menu returns Dunkin's one shared national menu — item names, descriptions, and photos grouped into categories — but no price or nutrition data; pricing varies by market and franchisee and isn't part of this content.
44 states at the root of /dunkin/directory — each with its own cities and stores beneath it in the tree.
Yes — both /dunkin/nearby and /dunkin/store return which third-party delivery platforms Dunkin' marks active for that specific store.
No — Dunkin' publishes one shared menu across every US store, confirmed live across stores in different states referencing the same underlying menu id, so /dunkin/menu takes no store id and always returns the same catalog regardless of location.