Restaurant locator and footprint mapping
Mit Five Guys-Endpunkten verwandelst du restaurant locator and footprint mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Five Guys' public restaurant data into structured JSON — free-text location search and coordinate proximity search off Five Guys' own Yext-backed locator (with in-store hours, a separate delivery schedule, amenity and service labels, and order links), a three-level state/city/restaurant directory browse, full per-restaurant profiles, a second ordering-platform locator with per-store names, the published marketing menu plus that same ordering platform's real per-item, per-restaurant priced menu, the 142-entry customer FAQ corpus, and a live-resolved link to the current nutrition and allergen guide. Credential-free.
Search Five Guys restaurants by location or coordinate, browse the directory, and get menus with real prices, FAQs, and the nutrition guide as JSON.
Endpunkt-Familien
6
Dokumentierte Parameter
36
Beispiele
10
Live-Katalog-Snapshot
Aktive Endpunkte
10
Methoden
GET
Pflichtparameter
16
Schema-Referenzen
10
{
"platform": "Five Guys",
"endpoint": "fiveguys-search",
"method": "GET",
"path": "/fiveguys/search",
"auth": "apiKey"
}Use Cases
Search Five Guys restaurants by location or coordinate, browse the directory, and get menus with real prices, FAQs, and the nutrition guide as JSON.
Mit Five Guys-Endpunkten verwandelst du restaurant locator and footprint mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Five Guys-Endpunkten verwandelst du menu and nutrition reference monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Five Guys-Endpunkten verwandelst du local retail presence monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Five Guys-Endpunktkatalog — 10 Endpunkte, 36 dokumentierte Request-Parameter und 10 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
10 documented Five Guys endpoints, grouped into 10 request families — Directory, Faq and Faq Categories, plus 7 more.
36 request parameters are documented across those Five Guys endpoints, 16 of them required — the full input contract is public before you write any integration code.
10 of the 10 Five Guys endpoints ship a recorded example response, and 10 carry a documented response schema — you can code against the real JSON before the first request.
Five Guys 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.
10 hosted MCP tools back the Five Guys endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
Diese Karten werden aus dem aktiven Endpunktkatalog generiert, damit die Landingpage dieselbe API-Oberfläche widerspiegelt, die auch Docs und Playground nutzen.
/fiveguys/directory
/fiveguys/faq
/fiveguys/faq-categories
/fiveguys/menu
/fiveguys/nearby
/fiveguys/nutrition
Endpunktkatalog
/fiveguys/searchReturns Five Guys restaurants matching a free-text location query -- a city, a zip/postal code, a street address, or a landmark -- the same way restaurants.fiveguys.com's own locator search box works. Yext's own query understanding geocodes the text server-side, so no separate geocoding call is needed. Each result carries a full profile: a short area/plaza label distinguishing it from other locations, address, phone, weekly in-store hours plus a separate delivery-hours schedule when published, price tier, restaurant-amenity labels (e.g. Takeout, Dine In, Curbside), pickup/delivery service labels, order/delivery/menu URLs, a Google Place id, and distance in miles/kilometers from the resolved query location. `total_results` reports how many restaurants matched overall, usually more than one page; use `offset` to page. A query that resolves to nowhere Five Guys operates returns an empty list rather than an error.
MCP-Tool fiveguys_search
/fiveguys/nearbyReturns Five Guys restaurants within a radius of a latitude/longitude. Each result carries a full profile: a short area/plaza label distinguishing it from other locations, address, phone, weekly in-store hours plus a separate delivery-hours schedule when published, price tier, restaurant-amenity labels (e.g. Takeout, Dine In, Curbside), pickup/delivery service labels, order/delivery/menu URLs, a Google Place id, and distance in miles/kilometers from the given coordinate. `total_results` reports how many restaurants fall inside the radius overall, usually more than one page; use `offset` to page. A coordinate with no Five Guys nearby returns an empty list rather than an error.
MCP-Tool fiveguys_nearby
/fiveguys/directoryReturns one level of Five Guys' US restaurant directory: the 50 states at the root, one state's cities when path is a state (e.g. `il`), and that city's restaurants when path is a city (e.g. `il/chicago`). Each child carries the path to pass back as this endpoint's `path`, and a `location_count` of how many restaurants sit under it. At the deepest level children are restaurants themselves (`is_location` true) -- pass their path to GET /fiveguys/store for the full profile. Use this to enumerate or browse locations; use GET /fiveguys/search or /fiveguys/nearby to find them by query or coordinate instead.
MCP-Tool fiveguys_directory
/fiveguys/storeReturns one Five Guys restaurant's full published profile by its locator slug -- address, phone, weekly in-store hours, separate delivery hours, coordinate, Google Place id, restaurant-amenity labels, and order/delivery/menu URLs. Get a path from GET /fiveguys/search or /fiveguys/nearby's `locations[].path`, or from GET /fiveguys/directory's `children[].path` where `is_location` is true. It also returns three detail-only extras that search and nearby results do not carry: `description` (this restaurant's own blurb, templated but genuinely per-location), `photos` (its published gallery images, omitted for the many locations that publish none), and `breadcrumbs` (the directory trail above it, each entry's `path` feeding straight back into GET /fiveguys/directory). Two fields available on search and nearby results are not published on this surface and are omitted here: `price_range` and `pickup_and_delivery_services`. A `profile` block, populated best-effort from a second Yext key, adds further per-restaurant detail no other field in this family carries: `google_attributes` (structured amenity flags, richer than `services`), `review_page_url`/`review_invite_url`, `featured_message`/`featured_message_url`, `google_cid`/`facebook_store_id`, `routable_latitude`/`routable_longitude` (a driving destination, distinct from the display coordinate), `payment_options`, `meals_served`, `services`, `permanently_closed`, `directory_listing_url`, `franchisee_group` (the operator of this specific restaurant -- a corporate code or a franchisee's own company name), `facebook_vanity_url` (this location's own Facebook handle), and `faq` (this restaurant's own generated question set, distinct from the national corpus GET /fiveguys/faq serves). Passing a state or city path returns 404 -- use GET /fiveguys/directory for those.
MCP-Tool fiveguys_store
/fiveguys/ordering-locationsReturns Five Guys restaurants near a latitude/longitude as Five Guys' own ordering platform publishes them, with commerce detail no other endpoint in this family carries: per-store delivery fee, delivery and pickup order minimums, whether the store is currently accepting orders at all, the handoff modes an order placed now could actually use (delivery, pickup, curbside, dine-in, drive-thru, dispatch), group-order/coupon/loyalty support, how many days ahead an order may be scheduled, and the store's own order URL. Set `include_hours` to also return each store's dated business and delivery calendars -- concrete dated windows rather than the recurring weekly schedule the locator endpoints publish, so they reflect holiday and special hours a weekly schedule cannot express. This is a different upstream from GET /fiveguys/nearby, which returns the marketing/locator record: the two describe the same restaurants but do not share ids, and this one carries a per-store name ("Five Guys Austin Arbor") where the locator publishes the generic brand name. Use each result's `id` with GET /fiveguys/ordering-menu for that store's priced menu. A coordinate with no Five Guys nearby returns an empty list rather than an error.
MCP-Tool fiveguys_ordering_locations
/fiveguys/ordering-menuReturns one restaurant's full menu exactly as Five Guys' own ordering platform sells it, including real per-item prices -- the one field no other endpoint in this family can surface (GET /fiveguys/menu is fiveguys.com's own marketing content and carries no price at all). Categories and items are returned with name, description, price, calories (a single value or a real range, e.g. a fountain drink sized at checkout), an image, and whether the platform currently has the item available. id is the ordering platform's own restaurant id from GET /fiveguys/ordering-locations' locations[].id -- it is not a Yext entity id and does not correspond to any id from GET /fiveguys/search, /fiveguys/nearby, /fiveguys/directory, or /fiveguys/store.
MCP-Tool fiveguys_ordering_menu
/fiveguys/menuReturns Five Guys' public menu content: every category (Burgers, Fries, Shakes, Hot Dogs, Sandwiches, Drinks, Toppings) -- each with its own short description and cover image, plus its items' name, description, calories, and image -- or one category's items when category is given. Five Guys publishes no per-item price on this surface -- pricing is store-scoped and lives only behind its ordering flow, which this endpoint does not cover. Available in English (default) and Spanish via `lang`. Calories are shown exactly as published: a single value for most items, or a range (e.g. fries' "530-1100") for build-your-own items whose calories vary by size and toppings. Some items (drink categories, a few build-your-own items) publish no calorie figure at all; their calories field is omitted rather than estimated.
MCP-Tool fiveguys_menu
/fiveguys/nutritionResolves the live location of Five Guys' current dated nutrition & allergen guide PDF (calories, full macro nutrition and allergen data per item) directly from fiveguys.com -- the guide's own file path changes when Five Guys republishes it (observed monthly), so this endpoint always discovers the current link rather than returning a fixed one. Returns the PDF's direct download URL plus best-effort size and last-modified metadata read from the PDF's own response headers. This endpoint returns metadata and a link to the guide, not its table parsed into structured fields -- pair it with GET /fiveguys/menu for structured per-item calories.
MCP-Tool fiveguys_nutrition
/fiveguys/faqReturns one page of Five Guys' published customer FAQ corpus -- 142 entries across 17 categories (Menu, Nutritional and Allergens, Ordering, Gift Card, Careers, Franchise, App, Company, The Crew, and others), filterable by category id and free text, in English (default) or Spanish via `lang`. Get valid category values from GET /fiveguys/faq-categories using the same `lang` -- category ids are language-specific.
MCP-Tool fiveguys_faq
/fiveguys/faq-categoriesReturns every published Five Guys FAQ category with its id, name, slug, and entry count -- use an id here as GET /fiveguys/faq's category filter. Available in English (default) and Spanish via `lang`; ids differ between languages, so pass the same `lang` to both endpoints.
MCP-Tool fiveguys_faq_categories
Verwandte 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.
So scrapst du Five Guys
Crawlora's Five Guys endpoints return normalized public Five Guys data as JSON with one API key — no Five Guys account required. Two distinct upstreams back this family: the Yext-powered marketing locator and Five Guys' own ordering platform, and they do not share store ids.
The search endpoint takes a free-text location query — a city, a zip or postal code, a street address, or a landmark — exactly the way restaurants.fiveguys.com's own search box works. Yext geocodes the query server-side, so no separate geocoding step is needed. When you already have a coordinate, the nearby endpoint takes a latitude and longitude with a radius instead. Both return the full profile: address, phone, weekly in-store hours, a separate delivery schedule (it can close earlier than the dining room), price tier, amenity labels, and order links.
The directory endpoint walks Five Guys' US locator one level at a time — omit path for the 50 states with their restaurant counts, pass a state such as il for its cities, and a state and city such as il/chicago for its restaurants. At the restaurant level children carry is_location true and the path to hand straight to the store endpoint.
Pass a locator path — from a search or nearby result, or a directory child flagged is_location — to the store endpoint for that restaurant's complete published profile, read from its own location page.
The ordering-locations endpoint returns the same physical restaurants near a coordinate as Five Guys' own ordering platform publishes them. It is a genuinely different upstream from the locator: the ids do not match, and it carries a per-store name such as Five Guys Austin Arbor where the locator only publishes the generic brand name.
The menu endpoint returns every category, or one category's items when a category is given, from fiveguys.com's own marketing content — no price. The FAQ endpoints cover Five Guys' published customer FAQ — list the categories first for their ids and entry counts, then filter the corpus by category or free text. The nutrition endpoint resolves the current dated nutrition and allergen guide PDF live, because Five Guys republishes it under a new file path roughly monthly.
The ordering-menu endpoint is the only one in this family that carries real per-item prices — it reads order.fiveguys.com itself rather than the marketing site. Pass an ordering-locations id (not a search/nearby/directory/store id — that upstream uses its own, unrelated identifiers) for that restaurant's full menu: every category and item with its price, a calorie range, an image where published, and the platform's own live availability flags.
FAQ
Search restaurants by a free-text location or a coordinate, browse the state/city directory, then pass a locator path to the store endpoint for one restaurant's full profile, and read the menu, FAQ corpus, and nutrition guide link — all return structured JSON with one API key.
Yes, from one endpoint only: the marketing menu endpoint publishes no per-item price at all, but the ordering-menu endpoint reads order.fiveguys.com directly and returns each item's real price for that specific restaurant, alongside a calorie range and live availability. It takes an ordering-locations id, not a search/nearby/directory/store id — those describe the same physical restaurants through a different upstream with its own, unrelated identifiers.
They read different upstreams. The nearby endpoint returns the marketing/locator record from Yext, while the ordering-locations endpoint returns the same physical restaurants as Five Guys' own ordering platform publishes them. Their store ids do not correspond, and only the ordering view carries a per-store name rather than the generic brand name.
The nutrition endpoint resolves the live location of Five Guys' current dated nutrition and allergen guide PDF. Five Guys republishes the guide under a new file path — observed roughly monthly — so the endpoint discovers the current link on each call rather than returning a fixed URL. It returns the link and its metadata, not the guide's table parsed into fields.
Often, yes — and the locator publishes them separately. Search and nearby results carry the weekly in-store hours alongside a distinct delivery-hours schedule where Five Guys publishes one, and delivery can stop earlier than the dining room closes, so read the delivery schedule rather than inferring it from opening hours.