Restaurant locator and footprint mapping
Zaxby'sエンドポイントを使えば、「Restaurant locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Zaxby's public store and menu data into structured JSON — coordinate proximity search read anonymously from Zaxby's own backend with no key or cookie, full per-store detail with per-channel hours and fulfillment flags, and the complete national reference menu with every category, product, description, calorie count, and a recursive customization tree of size, protein and sauce choices carrying their own price deltas. Credential-free.
Find Zaxby's stores near a coordinate, get full per-store detail, and pull the national reference menu with its customization tree as JSON.
エンドポイントファミリー
3
ドキュメント化されたパラメータ
8
サンプル数
3
ライブカタログスナップショット
稼働エンドポイント
3
メソッド
GET
必須パラメータ
6
スキーマ参照
3
{
"platform": "Zaxby's",
"endpoint": "zaxbys-nearby",
"method": "GET",
"path": "/zaxbys/nearby",
"auth": "apiKey"
}ユースケース
Find Zaxby's stores near a coordinate, get full per-store detail, and pull the national reference menu with its customization tree as JSON.
Zaxby'sエンドポイントを使えば、「Restaurant locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Zaxby'sエンドポイントを使えば、「Menu and customization reference monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Zaxby'sエンドポイントを使えば、「Local retail presence monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のZaxby'sエンドポイントカタログから取得しています（エンドポイント3件、ドキュメント化されたリクエストパラメータ8個、公開レスポンススキーマ3件）。DocsとPlaygroundが参照しているカタログと同じものです。
Zaxby'sのエンドポイントは3件、3つのリクエストファミリーに分類されています（Menu、Nearby、Store）。
これらのZaxby'sエンドポイントには8個のリクエストパラメータがドキュメント化されており、うち6個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
3件のZaxby'sエンドポイントのうち3件が実際のサンプルレスポンスを、3件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Zaxby'sのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Zaxby'sのエンドポイントは3個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/zaxbys/menu
/zaxbys/nearby
/zaxbys/store
エンドポイントカタログ
/zaxbys/nearbyReturns Zaxby's stores within a radius of a coordinate, nearest first: full address, phone, coordinates, current open status, per-channel hours (dine-in, drive-thru, carryout, pickup, delivery), and fulfillment/amenity flags. Each result's store_id pairs with GET /zaxbys/store for the same record on its own.
MCPツール zaxbys_nearby
/zaxbys/storeReturns one Zaxby's store's full detail by its store id: address, phone, coordinates, current open status, per-channel hours, and fulfillment/amenity flags. store_id comes from a GET /zaxbys/nearby result.
MCPツール zaxbys_store
/zaxbys/menuReturns Zaxby's full national reference menu: every category and product, with description, calories, image, and a full recursive customization tree (size/protein/sauce choices, each with its own real price delta). This is national reference data, not store-priced -- most items list cost 0 because real pricing is store-specific and requires a signed-in ordering session this endpoint does not have. Many items price entirely through a required customization selection rather than a base cost, so cost 0 on an item is expected, not a bug.
MCPツール zaxbys_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.
Zaxby'sのスクレイピング方法
Crawlora's Zaxby's endpoints return normalized public Zaxby's data as JSON with one API key — no Zaxby's account required. The store family reads Zaxby's own backend anonymously, and the menu is national reference data rather than a store-priced catalog.
The nearby endpoint takes a latitude and longitude with an optional radius in miles and a result limit, returning stores nearest first. It reads Zaxby's own backend directly and anonymously — no API key of its own, no cookie, no login — and each result's store id pairs with the store endpoint for the same record on its own.
Pass a store id from a nearby result to the store endpoint for that restaurant's complete record: address, phone, coordinates, current open status, hours broken out per order channel, and its fulfillment and amenity flags.
The menu endpoint returns Zaxby's full national reference menu — every category and product with description, calories, image, and a recursive customization tree covering size, protein and sauce choices, each option carrying its own real price delta.
Treat this menu as reference data, not a price list. Most items report a cost of zero because real pricing is store-specific and sits behind a signed-in ordering session this endpoint does not have, and many items genuinely price through a required customization selection rather than a base cost — so a zero base cost is not the same as a free item. Read the customization tree's deltas alongside it before drawing any pricing conclusion.
FAQ
Call the nearby endpoint with a latitude and longitude for stores nearest first, pass a store id to the store endpoint for that restaurant's full detail, and call the menu endpoint for the national reference menu with its customization tree — all return structured JSON with one API key.
Not real store prices. The menu is Zaxby's national reference catalog: most items report a cost of zero because pricing is store-specific and lives behind a signed-in ordering session this endpoint does not have. Many items also price entirely through a required customization selection, so a zero base cost is not a free item — read the customization tree's price deltas alongside it.
No. The nearby endpoint reads Zaxby's own backend directly and anonymously — no upstream API key, no cookie, and no login of any kind. The only credential anywhere in the flow is your Crawlora API key.
From the store endpoint. A nearby result gives you the store id and proximity; the store record adds the full detail — address, phone, coordinates, current open status, hours broken out per order channel, and the fulfillment and amenity flags for that location.
Yes — every product carries a recursive customization tree covering its size, protein and sauce choices, and each option in the tree carries its own real price delta rather than just a label. That tree is also where much of the item's actual price comes from, since many items have no meaningful base cost of their own.