Store locator and footprint mapping
Shake Shackエンドポイントを使えば、「Store locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Shake Shack's public store and menu data into structured JSON — the full store index parsed from the site's own map and text-list sections, coordinate-based nearby search against the live ordering API with real-time fulfillment-mode availability, per-store detail (address, coordinates, phone, hours, order types), and each location's full menu with customization trees and calorie deltas. Credential-free.
Browse Shake Shack's store index, find nearby locations with live ordering status, and get full store and menu detail as structured JSON.
エンドポイントファミリー
4
ドキュメント化されたパラメータ
12
サンプル数
4
ライブカタログスナップショット
稼働エンドポイント
4
メソッド
GET
必須パラメータ
8
スキーマ参照
4
{
"platform": "Shake Shack",
"endpoint": "shakeshack-locations",
"method": "GET",
"path": "/shakeshack/locations",
"auth": "apiKey"
}ユースケース
Browse Shake Shack's store index, find nearby locations with live ordering status, and get full store and menu detail as structured JSON.
Shake Shackエンドポイントを使えば、「Store locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Shake Shackエンドポイントを使えば、「Order-type and service-coverage research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Shake Shackエンドポイントを使えば、「Menu and customization monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Shake Shackエンドポイントを使えば、「Local retail presence monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のShake Shackエンドポイントカタログから取得しています（エンドポイント4件、ドキュメント化されたリクエストパラメータ12個、公開レスポンススキーマ4件）。DocsとPlaygroundが参照しているカタログと同じものです。
Shake Shackのエンドポイントは4件、4つのリクエストファミリーに分類されています（Locations、Menu、Nearbyほか1件）。
これらのShake Shackエンドポイントには12個のリクエストパラメータがドキュメント化されており、うち8個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
4件のShake Shackエンドポイントのうち4件が実際のサンプルレスポンスを、4件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Shake Shackのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Shake Shackのエンドポイントは4個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/shakeshack/locations
/shakeshack/menu
/shakeshack/nearby
/shakeshack/store
エンドポイントカタログ
/shakeshack/locationsReturns one page of Shake Shack's store index, parsed off the single, fully server-rendered /locations page. That page carries two independent sections: an interactive map (coordinates, no structured address) and an accessible "Full List of Locations" text index (structured address, no coordinates). Each entry's source field says which section it came from -- "map" or "list" -- not a business classification; both round-trip through GET /shakeshack/store by path, which always returns full structured address and coordinates regardless of source.
MCPツール shakeshack_locations
/shakeshack/nearbyReturns Shake Shack locations within a radius of a coordinate, nearest first, using Shake Shack's own Olo-backed ordering API (a separate source from GET /shakeshack/locations, which reads the main site's store directory instead). Each result carries location_id, real-time weekly hours, which fulfillment modes are currently enabled (dine-in, pickup, delivery, curbside, drive-thru, walk-up, drive-up), and Shake Shack's own delivery fee schedule. Pass location_id to GET /shakeshack/menu for that location's full menu.
MCPツール shakeshack_nearby
/shakeshack/storeReturns one Shake Shack store: postal address, coordinates, phone (when published), a Monday-first week of opening hours (omitted for a location that publishes no schedule, seen on venue/kiosk-shaped locations such as inside a stadium), and the order types Shake Shack publishes for it, e.g. "Dine In", "Delivery". Store paths come from GET /shakeshack/locations, either the aliased "location/<slug>" form or the legacy "node/<id>" form -- both resolve to the same record, and the response's own path field always reports the canonical alias. A path with neither shape, or one that does not resolve to a real store page, returns a 404.
MCPツール shakeshack_store
/shakeshack/menuReturns one Shake Shack location's full menu as a category tree: every category and its products, with name, description, base calories, allergens, a promotional/dietary badge when published (e.g. "LIMITED TIME ONLY", "VEGETARIAN"), image, and a full customization tree (size, additions, removals, allergen flags), each choice carrying its own price and calorie delta. location_id comes from GET /shakeshack/nearby. Many items, most notably burgers, price entirely through a required size selection rather than a base price, so price is commonly 0 for those items -- the real price lives on the size modifier's own choices.
MCPツール shakeshack_menu
関連API
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.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
Shake Shackのスクレイピング方法
Crawlora's Shake Shack endpoints return normalized public Shake Shack store and menu data as JSON with one API key — no Shake Shack account required.
Call /shakeshack/locations, paginated with page and page_size, for entries parsed off the site's single /locations page — its map section (coordinates, no structured address) and its accessible "Full List of Locations" text index (structured address, no coordinates). Each entry's source field says which section it came from; both round-trip through /shakeshack/store to the same full record.
Pass a latitude, longitude, and optional radius/limit to /shakeshack/nearby for the closest locations, nearest first, sourced from Shake Shack's own Olo-backed ordering API rather than the main-site directory — each result carries location_id, real-time weekly hours, and which fulfillment modes (dine-in, pickup, delivery, curbside, drive-thru, walk-up) are currently enabled.
Pass a path from /shakeshack/locations to /shakeshack/store for that location's postal address, coordinates, phone (when published), a Monday-first week of hours, and its published order types — hours are omitted for venue/kiosk-shaped locations (e.g. inside a stadium) that publish no schedule.
Store paths come in an aliased "location/<slug>" form or a legacy "node/<id>" form — both resolve to the same store record, and /shakeshack/store's response always reports the canonical alias in its own path field regardless of which form you passed.
Pass the location_id from /shakeshack/nearby to /shakeshack/menu for that location's complete category tree — every product with name, description, base calories, allergens, a promotional/dietary badge when published (e.g. "LIMITED TIME ONLY", "VEGETARIAN"), image, and a full customization tree (size, additions, removals, allergen flags) where each choice carries its own price and calorie delta.
FAQ
Call /shakeshack/locations to browse the store index or /shakeshack/nearby with a coordinate for the closest locations, pass a path to /shakeshack/store for full store detail, or a location_id to /shakeshack/menu for that location's menu — all return structured JSON with one API key.
/shakeshack/locations parses two independent sections of the site's own /locations page — an interactive map (coordinates only) and a text list (structured address only) — and reports which one a given entry came from via source. Calling /shakeshack/store for that same location always returns both, regardless of source.
No — venue/kiosk-shaped locations, such as one inside a stadium, can publish no schedule at all; /shakeshack/store omits hours for those rather than fabricating a week.
Whatever Shake Shack itself publishes for that specific store, e.g. "Dine In" or "Delivery" — not a fixed list, since availability varies by location.
/shakeshack/locations parses the main site's static store-directory page. /shakeshack/nearby is a separate, coordinate-based lookup against Shake Shack's own Olo-backed ordering API, returning real-time weekly hours and which fulfillment modes are currently enabled — live ordering status the directory page doesn't carry.
Yes — /shakeshack/menu returns each product's full customization tree (size, additions, removals, allergen flags), with every choice carrying its own price and calorie delta, plus base calories, allergens, and any published promotional or dietary badge.
Many items, most notably burgers, price entirely through a required size selection rather than a base price — the real price lives on that item's "Select Size" modifier group (e.g. Single, Double, Triple), not a parsing gap.