Cafe locator and footprint mapping
Use Panera endpoints to turn cafe locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Turn Panera Bread's public ordering data into structured JSON — the full US cafe locator tree, per-cafe menus and catering menus with genuinely per-cafe pricing and nutrition, item detail and customization options, order time-slots, quantity limits, retired and seasonal items, upsell suggestions, and the separate Panera at Work workplace-delivery program. Credential-free.
Browse Panera Bread's cafe locator, get per-cafe menus with pricing and nutrition, and pull catering, time-slot, and item-customization data as structured JSON.
Endpoint families
6
Documented params
29
Examples
13
Live catalog snapshot
Active endpoints
13
Methods
GET
Required params
27
Schema refs
13
{
"platform": "Panera",
"endpoint": "panera-locations",
"method": "GET",
"path": "/panera/locations",
"auth": "apiKey"
}Use cases
Browse Panera Bread's cafe locator, get per-cafe menus with pricing and nutrition, and pull catering, time-slot, and item-customization data as structured JSON.
Use Panera endpoints to turn cafe locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Use Panera endpoints to turn per-cafe menu and pricing monitoring into repeatable API requests with documented inputs and JSON responses.
Use Panera endpoints to turn catering and nutrition data research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Panera endpoint catalog — 13 endpoints, 29 documented request parameters, and 13 published response schemas — the same catalog Docs and Playground run against.
13 documented Panera endpoints, grouped into 13 request families — At Work Locations, Cafe and Catering Delivery Info, plus 10 more.
29 request parameters are documented across those Panera endpoints, 27 of them required — the full input contract is public before you write any integration code.
13 of the 13 Panera endpoints ship a recorded example response, and 13 carry a documented response schema — you can code against the real JSON before the first request.
Panera 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.
13 hosted MCP tools back the Panera 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.
/panera/at-work-locations
/panera/cafe
/panera/catering-delivery-info
/panera/catering-menu
/panera/geocode
/panera/item-detail
Featured endpoints
/panera/locationsReturns one level of Panera Bread's US cafe locator tree. Omit both state and city to list every US state and territory Panera serves, each with its cafe count. Pass state to list every city in that state, each with its full cafe list -- id, name, street address, city, state, postal code, phone, coordinates and per-cafe amenity flags (for example hasDriveThru, hasDelivery, hasCurbside, hasKiosk). Pass both state and city to narrow to that one city's cafes. A state Panera does not serve, or a city with no match, returns an empty list rather than an error.
MCP tool panera_locations
/panera/cafeReturns one Panera Bread cafe's address, phone, coordinates, amenity flags, per-fulfillment-channel availability (dine-in, storefront/pickup, rapid pickup, drive-thru, curbside, delivery -- each with its own available/open-now/lead-time-minutes and weekly hours where Panera publishes them) and the published storefront hours for the next calendar week with concrete dates. Cafe ids come from GET /panera/locations. An unknown cafe id returns a 404.
MCP tool panera_cafe
/panera/menuReturns one cafe's full category tree (with subcategories) and its complete item catalog, priced for that specific cafe -- Panera's prices are genuinely per-cafe, not a national list (the same salad has been confirmed live at different prices in Chicago and New York). Each item carries its price, product type, whether it is customizable, its published nutrients (Panera's placard API only ever publishes Calories and Caffeine on this surface -- a fuller macro/micronutrient breakdown is not available credential-free), its allergen statement (contains / may-contain, each with an id and display name), Panera's own wellness/dietary labels (for example Vegan, Vegetarian, Gluten Conscious), and a live in_stock flag from this cafe's current stockout feed. Cafe ids come from GET /panera/locations. An unknown cafe id returns a 404.
MCP tool panera_menu
/panera/item-detailReturns one menu item's full description, ingredient statement, a full per-serving nutrient panel (richer than GET /panera/menu's calories/caffeine-only surface), its allergen statement, and every selectable size with its own price and calories. item_id may be negative -- GET /panera/menu itself surfaces negative item ids for some items, and they resolve fine here. Returns 404 if Panera publishes no detail page for the given item id at this cafe.
MCP tool panera_item_detail
/panera/item-optionsReturns one item's selectable option groups: for a combo, each group is a slot to fill (for example "pick 4 sandwiches", "pick 1 soup"), listing every eligible choice; for a single customizable item, each group is one topping/add-in/amount choice (for example No, Light, Regular, Extra). Each group has min_allowed and max_allowed (how many selections it requires). Each option is one selectable choice, with its own selectable variants (amount tiers) each carrying an item_id and price -- price 0 for a variant included at no extra charge. Panera does not publish a resolved display name for options or groups on this surface, so each option carries its raw upstream image_key as the caller-facing identifier instead of a name. An item that is not customizable, or an unknown item id, returns an empty groups list rather than an error -- Panera's own API does not distinguish the two cases. Item ids come from GET /panera/menu.
MCP tool panera_item_options
/panera/catering-menuReturns one cafe's catering category list and its full catering item catalog, priced for that specific cafe -- Panera's catering ordering flow is a separate application from its retail site, with its own category structure, pricing and item availability (confirmed live: the same item priced differently between a placeholder default cafe and a real cafe). Categories are a flat list (catering does not publish a category hierarchy the way the retail menu does). Each item carries its price, product type, portion label, whether it is customizable, a full published nutrient panel (calories, calories from fat, fat, saturated fat, trans fat, cholesterol, sodium, carbohydrates, dietary fiber, total sugars, protein, caffeine -- richer than the retail menu's calories/caffeine-only surface), its allergen statement (contains / may-contain, each with an id and display name), and a live in_stock flag from this cafe's current catering stockout feed for today. Cafe ids come from GET /panera/locations.
MCP tool panera_catering_menu
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 Panera
Crawlora's Panera endpoints return normalized public Panera Bread data as JSON with one API key — no Panera account required. Prices, nutrition, and stock genuinely vary per cafe, so most endpoints take a cafe_id from /panera/locations.
Call /panera/locations with no parameters for every US state and territory Panera serves with cafe counts, pass state to list that state's cities and cafes, or pass both state and city to narrow to one city. Use /panera/geocode to resolve a free-text address or postal code to coordinates first, the same lookup Panera's own site uses to center a search.
Call /panera/cafe with a cafe_id for address, amenities, and per-channel availability (dine-in, pickup, drive-thru, curbside, delivery), or /panera/menu for that cafe's full priced catalog with nutrition, allergens, wellness labels, and a live in_stock flag — Panera's prices are genuinely per-cafe, confirmed different between cities for the same item.
Pass a cafe_id and item_id to /panera/item-detail for a fuller nutrient panel and every selectable size with its own price, or /panera/item-options for the pick-groups a combo or customizable item accepts, each option carrying its own price delta.
Call /panera/catering-menu for a cafe's separate catering catalog — its own category structure and per-cafe pricing, distinct from the retail menu — and /panera/catering-delivery-info for delivery fees, minimums, and lead-time tiers.
Use /panera/time-slots for a date's live order-slot availability, /panera/quantity-rules for per-order caps on limited items, /panera/retired-products for discontinued or seasonal items, /panera/upsell-suggestions for Panera's own add-on recommendations, and /panera/at-work-locations for the separate national B2B workplace-delivery program.
FAQ
Call /panera/locations to browse cafes by state and city, /panera/cafe and /panera/menu for a cafe's detail and priced menu, /panera/item-detail and /panera/item-options for full item and customization data, or /panera/catering-menu for catering — all return structured JSON with one API key.
Yes — Panera's prices are genuinely per-cafe, not a national list; the same item has been confirmed live at different prices in different cities. Always pass the specific cafe_id you care about rather than assuming one cafe's pricing applies elsewhere.
/panera/menu's placard surface only publishes Calories and Caffeine per item; for a fuller macro and micronutrient breakdown, allergen statement, and per-size calories, use /panera/item-detail instead.
No — /panera/catering-menu is a separate application with its own category structure, pricing, and item availability from the retail menu; the same item has been confirmed priced differently between the two flows.
A separate national B2B workplace-delivery program from ordinary cafe pickup or delivery — /panera/at-work-locations returns its own drop-off locations, lead times, and per-weekday cutoff schedule, serviced by a specific cafe_id but distinct from that cafe's regular ordering hours.