Store enumeration and footprint mapping
Whataburgerエンドポイントを使えば、「Store enumeration and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Whataburger's own sitemap-declared store index into structured JSON — about 3,950 URLs from a single flat sitemap, each entry typed by kind, plus full per-store detail for any store path. Credential-free.
Enumerate Whataburger's ~3,950-URL store index and get full per-store detail as structured JSON.
エンドポイントファミリー
2
ドキュメント化されたパラメータ
6
サンプル数
2
ライブカタログスナップショット
稼働エンドポイント
2
メソッド
GET
必須パラメータ
3
スキーマ参照
2
{
"platform": "Whataburger",
"endpoint": "whataburger-sitemap",
"method": "GET",
"path": "/whataburger/sitemap",
"auth": "apiKey"
}ユースケース
Enumerate Whataburger's ~3,950-URL store index and get full per-store detail as structured JSON.
Whataburgerエンドポイントを使えば、「Store enumeration and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Whataburgerエンドポイントを使えば、「Local retail presence monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Whataburgerエンドポイントを使えば、「Store-count benchmarking against competitor chains」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のWhataburgerエンドポイントカタログから取得しています（エンドポイント2件、ドキュメント化されたリクエストパラメータ6個、公開レスポンススキーマ2件）。DocsとPlaygroundが参照しているカタログと同じものです。
Whataburgerのエンドポイントは2件、2つのリクエストファミリーに分類されています（Sitemap、Store）。
これらのWhataburgerエンドポイントには6個のリクエストパラメータがドキュメント化されており、うち3個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
2件のWhataburgerエンドポイントのうち2件が実際のサンプルレスポンスを、2件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Whataburgerのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Whataburgerのエンドポイントは2個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/whataburger/sitemap
/whataburger/store
エンドポイントカタログ
/whataburger/sitemapReturns one page of Whataburger's sitemap-declared store index -- about 3,950 URLs at time of writing. Unlike some other store locators in this API, Whataburger publishes a single flat sitemap file rather than a sharded index. Each entry carries a kind: "store" is a restaurant's canonical detail page, "curbside" and "delivery" are separate pages Whataburger publishes for that same restaurant's curbside or delivery service, and "directory" is a state- or city-level listing page with no address of its own. Filter with kind to enumerate one page variant. A page past the end returns an empty list rather than an error, so a caller can walk to exhaustion.
MCPツール whataburger_sitemap
/whataburger/storeReturns one Whataburger store: postal address, coordinates, phone, published week of opening hours, the restaurant services (curbside, delivery) Whataburger lists for it, and a per-channel hours breakdown (dine-in, drive-thru, curbside, delivery) where the channel's hours genuinely differ from the store's top-level hours. Store paths come from GET /whataburger/sitemap -- a store's canonical, curbside and delivery page paths all describe the same physical restaurant and return the same address; the response's own path field always reports the canonical page. Passing a state or city directory path returns a 404 rather than a hollow record. Note there is no menu source, so this family is a locator only.
MCPツール whataburger_store
関連API
Marketplaces & Retail
Separate an auction that is still open from a completed sale, and use BaT's own make and model directory to carry valid IDs into search and price-history requests.
Marketplaces & Retail
Treat Glovo as a local marketplace: discover the supported city first, then follow that city's category, store, menu, and collection identifiers through the catalog.
Marketplaces & Retail
Use PetSmart's hierarchical paths to scope product searches, then keep product SKU, price range, online availability, pickup eligibility, and store inventory as separate fields.
Whataburgerのスクレイピング方法
Crawlora's Whataburger endpoints return normalized public Whataburger store data as JSON with one API key — no Whataburger account required. Unlike Subway and Jimmy John's, Whataburger publishes a single flat sitemap rather than a sharded index. A pull on 2026-10-27 showed the sitemap route listing 3,969 entries across 794 pages at 5 per page, each with a kind, a store number and a path for the store route.
Call /whataburger/sitemap to page through Whataburger's sitemap-declared store index — about 3,950 URLs at time of writing. Each entry carries a kind, and because Whataburger publishes one flat sitemap.xml rather than a sharded index, there is no shard parameter to walk.
/whataburger/store with a sitemap path such as 1197C.html returned store_id 1197, address, phone_number, latitude, longitude and a per-day hours list. The sitemap listed 3,971 entries over 795 pages at page_size 5 on 2026-10-30, and one store appears under several kinds (1197C curbside, 1197D delivery), so de-duplicate by store_number before counting restaurants.
Page through /whataburger/sitemap until the response comes back empty to know you've reached the end of the index, then resolve whichever store paths you need.
sitemap with page_size 5 returned total 3,969 and total_pages 794. Entries carry a kind (the first was curbside), a store_number (1197) and a path such as 1197C.html, which is the value the store route takes.
The store route needs the path from the sitemap, so crawl the sitemap first and store the kind with each entry.
エージェントスキル
Crawlora のエージェントスキルをインストールすると、スクレイパーを書かずに、ドキュメント化された API 経由で Whataburger のデータを JSON として取得できます。Whataburger に対応するスキル:
Researches restaurants and grocery/food delivery via the Crawlora API — Yelp reviews, OpenTable reservations, DoorDash and Uber Eats restaurant…
npx skills add github.com/Crawlora-org/crawlora-skills --skill restaurant-food-delivery-researchFAQ
Call /whataburger/sitemap to page through the store-URL index, then pass a store path to /whataburger/store for that location's full detail — both return structured JSON with one API key.
About 3,950 URLs at time of writing. Not every URL is a store page — each entry carries a kind, so filter on it to separate stores from other page types.
No — unlike Subway and Jimmy John's, Whataburger publishes a single flat sitemap.xml, so /whataburger/sitemap takes no shard parameter; just page through it.
Not in this first pass — this family covers the store index and per-store detail only.
3,969 entries on 2026-10-27. Entries have a kind, so check how multiple entries for the same store number are classified before counting restaurants.