Restaurant locator and footprint mapping
Usa los endpoints de KFC para convertir restaurant locator and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
Turn KFC's public ordering data into structured JSON — restaurant search and lookup by store number, per-channel priced menus, delivery serviceability and fee estimates for a real address, and public promotions by restaurant or redemption code. Credential-free.
Find KFC restaurants, get restaurant-specific priced menus, check delivery serviceability, and look up promotions as structured JSON.
Familias de endpoints
6
Parámetros documentados
39
Ejemplos
7
Snapshot en vivo del catálogo
Endpoints activos
7
Métodos
GET
Parámetros obligatorios
20
Referencias de esquema
7
{
"platform": "KFC",
"endpoint": "kfc-nearby",
"method": "GET",
"path": "/kfc/nearby",
"auth": "apiKey"
}Casos de uso
Find KFC restaurants, get restaurant-specific priced menus, check delivery serviceability, and look up promotions as structured JSON.
Usa los endpoints de KFC para convertir restaurant locator and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de KFC para convertir menu and channel-pricing monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de KFC para convertir delivery serviceability and fee research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de KFC para convertir promotion and coupon tracking en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de KFC — 7 endpoints, 39 parámetros de solicitud documentados y 7 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
7 documented KFC endpoints, grouped into 7 request families — Delivery Estimate, Menu and Nearby, plus 4 more.
39 request parameters are documented across those KFC endpoints, 20 of them required — the full input contract is public before you write any integration code.
7 of the 7 KFC endpoints ship a recorded example response, and 7 carry a documented response schema — you can code against the real JSON before the first request.
KFC 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 KFC endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
/kfc/delivery-estimate
/kfc/menu
/kfc/nearby
/kfc/promotion
/kfc/promotions
/kfc/store
Catálogo de endpoints
/kfc/nearbyReturns KFC restaurants near a latitude/longitude, nearest first. A coordinate with no nearby KFC returns an empty list rather than an error. Each restaurant carries its store number, full address with coordinates, phone, whether it currently accepts online orders, its timezone, and its distance from the search point in miles. occasion restricts results to restaurants that offer a given order channel (e.g. only drive-thru locations).
Herramienta MCP kfc_nearby
/kfc/storesReturns KFC restaurants matching a city/state/postal code/name/franchise code/store number filter. At least one filter is required -- an unfiltered call would enumerate every US restaurant in one response, which this endpoint intentionally does not expose. Each restaurant carries its store number (the value /kfc/menu and /kfc/promotions take), full address with coordinates, phone, whether it currently accepts online orders, and its timezone. appear_in_store_results (default true) excludes internal/test records KFC's own storefront does not surface in customer-facing search -- a raw filter can otherwise return non-orderable administrative entries alongside real restaurants.
Herramienta MCP kfc_stores
/kfc/storeReturns one KFC restaurant's detail by its exact store number, from /kfc/stores or /kfc/nearby, including its recurring open hours per order channel (carryout, delivery, dine-in, drive-thru, catering carryout). A channel this restaurant does not offer at all is omitted from hours rather than reported as always-closed.
Herramienta MCP kfc_store
/kfc/menuReturns one restaurant's full menu grouped into categories (e.g. "Deals", "Combos", "Tenders"). Every entry is a product, a bundle (a combo or family meal), or a standalone priced variant -- type tells callers which -- and carries a price in USD cents plus a decimal dollar value, and an image when the upstream publishes one. Prices reflect this specific restaurant and order channel, not a national default. channel selects which order channel the menu is priced for (web ordering by default); prices can genuinely differ by channel (e.g. a delivery-marketplace channel vs. web).
Herramienta MCP kfc_menu
/kfc/delivery-estimateChecks whether a KFC restaurant's delivery integration can deliver to a given address and, when it can, the estimated delivery fee (broken down by fee line item) and pickup/dropoff time. This reads the same checkout-time estimate KFC's own site calls -- it does not add an item to a cart or place an order, and takes no payment or account information. serviceable is true only when the upstream returned a real estimate; a false value with reason populated covers every other case seen live: the delivery provider not enabled at this store, the address being outside the delivery zone, or the delivery marketplace itself reporting the store temporarily inactive. order_subtotal materially affects the fee estimate (KFC's own fee schedules can vary by order size), so it is required rather than defaulted. pickup_at defaults to 30 minutes from now (an "order now" style estimate) when omitted.
Herramienta MCP kfc_delivery_estimate
/kfc/promotionsReturns one restaurant's current public promotions -- current deals and offers KFC's storefront marks as public, with each promotion's id, internal and display name, description, whether it applies automatically, and active redemption codes when KFC exposes them. The returned codes can be passed to kfc-promotion. A store with no active public promotions returns an empty list rather than an error.
Herramienta MCP kfc_promotions
/kfc/promotionReturns one promotion by its redemption code (the code a customer types in at checkout) or its serialized code (a unique per-print QR/serial code, e.g. from a printed coupon, that resolves to a shared redemption code and its promotion). Exactly one of code or serialized_code is required. A serialized-code lookup additionally returns that code's own usage metadata (redemption_code, times_used, code_status, group_status, effective_date, expiration_date) alongside the promotion. An unknown or expired code returns a 404 rather than a null success payload.
Herramienta MCP kfc_promotion
APIs relacionadas
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
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.
Cómo hacer scraping de KFC
Crawlora's KFC endpoints return normalized public KFC US ordering data as JSON with one API key — no KFC account required. Prices reflect one specific restaurant and order channel, not a national default.
Pass a latitude and longitude to /kfc/nearby for nearby restaurants nearest first, or filter by city, state, postal code, name, franchise code, or store number with /kfc/stores — at least one filter is required, since an unfiltered call would enumerate every US restaurant.
Pass a store_number to /kfc/menu for that restaurant's full menu grouped into categories (Deals, Combos, Tenders, and more) — each entry typed as a product, bundle, or standalone variant, priced for the order channel you select.
Pass a store_number to /kfc/store for its recurring open hours broken out per order channel (carryout, delivery, dine-in, drive-thru, catering carryout) — a channel this restaurant doesn't offer at all is omitted rather than reported as always-closed.
Call /kfc/delivery-estimate with a store_number, a delivery address, and an order_subtotal for whether delivery can reach that address and, if so, the estimated fee breakdown and pickup/dropoff time — the same checkout-time check KFC's own site runs, without adding anything to a cart.
Call /kfc/promotions with a store_number for its current public deals, or /kfc/promotion with a redemption code or serialized code to resolve one specific promotion and its usage metadata.
Preguntas frecuentes
Call /kfc/nearby or /kfc/stores for restaurant search, /kfc/store for one restaurant's detail and hours, /kfc/menu for its priced menu, /kfc/delivery-estimate for delivery serviceability, or /kfc/promotions and /kfc/promotion for deals — all return structured JSON with one API key.
Yes — /kfc/menu prices reflect the specific restaurant and order channel you request (web ordering by default via the channel parameter), not a national price list; a delivery-marketplace channel can genuinely price differently than web.
No. It reads the same checkout-time estimate KFC's own site calls to check serviceability and fee — it does not add an item to a cart, place an order, or take payment or account information.
Any of: the delivery provider isn't enabled at this store, the address is outside the delivery zone, or the delivery marketplace itself reports the store temporarily inactive — the reason field explains which.
Yes — pass the coupon's serialized_code to /kfc/promotion. That returns the code's own usage metadata (times used, status, effective/expiration dates) alongside the promotion it resolves to, in addition to a plain redemption-code lookup.