Restaurant locator and footprint mapping
Use Culver's endpoints to turn restaurant locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Turn Culver's public restaurant and menu data into structured JSON — a directory of roughly 1,121 restaurants, the national menu's categories (ButterBurgers, Chicken, Fish & Seafood, Combos & Baskets, Frozen Custard, and more), full item detail with size and topping modifier trees, and per-restaurant detail including today's Flavor of the Day. Credential-free.
Browse Culver's ~1,121-restaurant directory and national menu, and get item, store, and the full flavor-of-the-day calendar as structured JSON.
Endpoint families
6
Documented params
15
Examples
7
Live catalog snapshot
Active endpoints
7
Methods
GET
Required params
13
Schema refs
7
{
"platform": "Culver's",
"endpoint": "culvers-directory",
"method": "GET",
"path": "/culvers/directory",
"auth": "apiKey"
}Use cases
Browse Culver's ~1,121-restaurant directory and national menu, and get item, store, and the full flavor-of-the-day calendar as structured JSON.
Use Culver's endpoints to turn restaurant locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Use Culver's endpoints to turn menu catalog and modifier research into repeatable API requests with documented inputs and JSON responses.
Use Culver's endpoints to turn flavor of the day tracking into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Culver's endpoint catalog — 7 endpoints, 15 documented request parameters, and 7 published response schemas — the same catalog Docs and Playground run against.
7 documented Culver's endpoints, grouped into 7 request families — Calendar, Categories and Directory, plus 4 more.
15 request parameters are documented across those Culver's endpoints, 13 of them required — the full input contract is public before you write any integration code.
7 of the 7 Culver's endpoints ship a recorded example response, and 7 carry a documented response schema — you can code against the real JSON before the first request.
Culver's endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
7 hosted MCP tools back the Culver's endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/culvers/calendar
/culvers/categories
/culvers/directory
/culvers/flavor
/culvers/item
/culvers/menu
Endpoint catalog
/culvers/directoryReturns one page of Culver's own restaurant-URL sitemap (~1,121 restaurants). Each entry's slug is the value GET /culvers/store takes.
MCP tool culvers_directory
/culvers/storeReturns one Culver's restaurant's address, phone, coordinates, open/closed status, fulfillment hours, handoff options, online-order link, and today's flavor(s) of the day. slug comes from GET /culvers/directory.
MCP tool culvers_store
/culvers/calendarReturns the full published schedule for one Culver's restaurant: the flavor of the day for every upcoming calendar date, plus the soups served on each date. Culver's publishes roughly a two-month forward window, and the schedule is genuinely per-restaurant -- two restaurants on the same date routinely feature different soups. slug comes from GET /culvers/directory. GET /culvers/store returns only today's and tomorrow's flavor; use this endpoint for the whole calendar.
MCP tool culvers_calendar
/culvers/categoriesReturns Culver's national menu's category list -- ButterBurgers, Chicken, Fish & Seafood, Combos & Baskets, Sides, Frozen Custard, Beverages and others -- each with its slug (the value GET /culvers/menu takes), a featured flag, and sort order.
MCP tool culvers_categories
/culvers/menuReturns the items in one Culver's menu category, each with name, description, image, and a link to Culver's nutrition guide. Category slugs come from GET /culvers/categories. Prices are not published on the national catalog -- Culver's only prices items once a specific restaurant is selected client-side, and no credential-free per-restaurant pricing source was found; see GET /culvers/item for full modifier/topping detail.
MCP tool culvers_menu
/culvers/itemReturns one Culver's menu item's full detail, including its size/topping modifier tree with each option's own calories and nutrition link. category and item slugs come from GET /culvers/categories and GET /culvers/menu.
MCP tool culvers_item
/culvers/flavorReturns one Fresh Frozen Custard flavor's full detail, including its declared allergens, a component-by-component ingredient breakdown, and Culver's own flavor-category labels. slug comes from GET /culvers/calendar (flavors[].slug) or GET /culvers/store (flavors_of_the_day[].slug).
MCP tool culvers_flavor
Related APIs
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.
How to scrape Culver's
Crawlora's Culver's endpoints return normalized public Culver's data as JSON with one API key — no Culver's account required. Culver's national menu carries no price field — see the FAQ below for why.
Call /culvers/directory, paginated with page and page_size, for Culver's own restaurant-URL index — roughly 1,121 restaurants. Each entry's slug is what /culvers/store takes.
Pass a slug from /culvers/directory to /culvers/store for that restaurant's address, phone, coordinates, open/closed status, per-channel fulfillment hours (dine-in, drive-thru, curbside), handoff options, and today's Flavor(s) of the Day — Culver's own featured Fresh Frozen Custard flavor, with name, description, date, and image.
Call /culvers/categories for the category list (ButterBurgers, Chicken, Fish & Seafood, Combos & Baskets, Sides, Frozen Custard, Beverages, and more), then /culvers/menu with a category slug for that category's items — name, description, image, and a link to Culver's nutrition guide.
Pass a slug to /culvers/calendar for that restaurant's whole published schedule — roughly a two-month forward window of the Fresh Frozen Custard flavor for every date, plus the soups served each day. /culvers/store returns only the current and next flavor, and the schedule is genuinely per-restaurant: two restaurants on the same date routinely feature different soups.
Pass a category and item slug from /culvers/menu to /culvers/item for that item's full size/topping modifier tree, each option carrying its own calories and nutrition link.
FAQ
Call /culvers/directory to browse the restaurant index, pass a slug to /culvers/store for full restaurant detail, /culvers/categories and /culvers/menu for the national menu, or /culvers/item for full modifier detail — all return structured JSON with one API key.
No — every item's cost on the national catalog is always the literal 0. Culver's, like several other national reference catalogs, publishes menu content location-agnostically and only prices items once a specific restaurant is selected client-side; no credential-free per-restaurant pricing source was found, so this endpoint exposes catalog content without a price field rather than a misleading always-zero one.
Culver's signature featured Fresh Frozen Custard flavor, which rotates daily per restaurant. /culvers/store returns the current or nearby-date flavor(s) with name, description, date, and image.
Roughly 1,121 at time of writing, paginated through /culvers/directory with page and page_size.
Yes — /culvers/calendar returns the whole window that restaurant publishes (roughly two months forward), one flavor entry per date plus the soups served each day. /culvers/store only carries the current and next flavor. Soup entries repeat dates, since a restaurant typically serves two to four soups a day.