Restaurant directory and footprint mapping
Chick-fil-Aエンドポイントを使えば、「Restaurant directory and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Chick-fil-A's public content into structured JSON — a 3,467-restaurant directory with address and hours, a 567-item menu catalog with taxonomy filters, a 522-entry customer FAQ corpus, and the full editorial family (press releases, blog stories, legal documents, press-kit assets). Credential-free.
Browse Chick-fil-A's restaurant directory, menu catalog, press and editorial content, and customer FAQs as structured JSON.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
37
サンプル数
8
ライブカタログスナップショット
稼働エンドポイント
8
メソッド
GET
必須パラメータ
11
スキーマ参照
8
{
"platform": "Chick-fil-A",
"endpoint": "chick-fil-a-locations",
"method": "GET",
"path": "/chick-fil-a/locations",
"auth": "apiKey"
}ユースケース
Browse Chick-fil-A's restaurant directory, menu catalog, press and editorial content, and customer FAQs as structured JSON.
Chick-fil-Aエンドポイントを使えば、「Restaurant directory and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Chick-fil-Aエンドポイントを使えば、「Menu catalog and taxonomy research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Chick-fil-Aエンドポイントを使えば、「Press, editorial, and FAQ content monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のChick-fil-Aエンドポイントカタログから取得しています（エンドポイント8件、ドキュメント化されたリクエストパラメータ37個、公開レスポンススキーマ8件）。DocsとPlaygroundが参照しているカタログと同じものです。
Chick-fil-Aのエンドポイントは8件、8つのリクエストファミリーに分類されています（Content、Content Taxonomy、Faqほか5件）。
これらのChick-fil-Aエンドポイントには37個のリクエストパラメータがドキュメント化されており、うち11個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
8件のChick-fil-Aエンドポイントのうち8件が実際のサンプルレスポンスを、8件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Chick-fil-Aのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Chick-fil-Aのエンドポイントは8個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/chick-fil-a/content
/chick-fil-a/content-taxonomy
/chick-fil-a/faq
/chick-fil-a/location
/chick-fil-a/locations
/chick-fil-a/menu
エンドポイントカタログ
/chick-fil-a/locationsReturns one page of Chick-fil-A's restaurant directory (3,467 restaurants at time of writing): each restaurant's id, slug, name, US state and its page URL. search filters by free text over restaurant names and is relevance-ranked; without it restaurants come back alphabetically so a caller can page through the whole directory deterministically. This index deliberately carries no address or hours -- Chick-fil-A does not expose them on the directory listing. Pass a slug from here to GET /chick-fil-a/location to get street address and opening hours for one restaurant.
MCPツール chick_fil_a_locations
/chick-fil-a/locationReturns one Chick-fil-A restaurant's street address, opening hours, cuisine description and photo, selected by either its numeric id or its slug (supply exactly one of the two -- passing both is rejected). opening_hours carries one entry per day; a day Chick-fil-A publishes as closed (notably every Sunday, and every day for a seasonal or food-truck location that is not currently operating) comes back with closed=true and empty opens/closes rather than a placeholder time. This response carries a postal address but no latitude/longitude -- Chick-fil-A does not publish coordinates for its restaurants, and this endpoint does not synthesize them.
MCPツール chick_fil_a_location
/chick-fil-a/menuReturns one page of Chick-fil-A's published menu catalog (567 items at time of writing): item name, slug, Chick-fil-A's own item tag, an ordering deep link, and the taxonomy term ids the item belongs to. Every id in a response's menu_taxonomy_ids, menu_item_type_ids, menu_item_group_ids and nutrition_table_menu_ids is a ready-to-use filter value for a follow-up call, and GET /chick-fil-a/menu-taxonomy lists each taxonomy's terms with their names. search filters by free text and is ranked by relevance; without it items come back alphabetically so a caller can page through the whole catalog deterministically. Note this catalog carries no prices or nutrition values -- Chick-fil-A does not publish either through this source.
MCPツール chick_fil_a_menu
/chick-fil-a/menu-itemReturns one Chick-fil-A menu item, selected by either its numeric id or its slug (supply exactly one of the two -- passing both is rejected). Unlike the listing endpoint, this resolves the item's taxonomy term ids to names, so menu_sections, item_types, item_groups and nutrition_tables each come back as {id, name, slug} triples rather than bare ids. Term resolution is best-effort: if the taxonomy lookups fail the item is still returned with ids and empty names rather than failing the whole call. This item detail carries no price and no nutrition values -- Chick-fil-A does not publish either through this source.
MCPツール chick_fil_a_menu_item
/chick-fil-a/menu-taxonomyReturns one page of terms for a single Chick-fil-A menu taxonomy, with each term's id, name, slug, parent and how many menu items carry it. This is how to discover the filter ids GET /chick-fil-a/menu accepts. taxonomy must be one of `menu_taxonomy` (customer-facing menu section -- Breakfast, Beverages, Catering Entrées, ... 36 terms), `menu_item_type` (`ITEM`, `ITEM_GROUPING`, `MODIFIER` -- 3 terms), `menu_item_group` (the grouping a variant belongs to, e.g. "Bacon, Egg & Cheese Biscuit" -- 100+ terms), or `nutrition_table_menu` (the grouping used by Chick-fil-A's published nutrition tables -- 18 terms). Terms come back alphabetically.
MCPツール chick_fil_a_menu_taxonomy
/chick-fil-a/faqReturns one page of Chick-fil-A's published customer FAQ corpus (522 entries at time of writing) across 30 categories -- Chick-fil-A One membership, points and rewards, digital ordering and payment, delivery support, sweepstakes terms, and more. Each entry carries the question, the answer as plain text, the answer's original HTML (a fair number of answers use links, lists and tables that plain text loses), and its resolved categories. Every categories[].id is a ready-to-use value for the category filter. search matches over question and answer text and is relevance-ranked; without it entries come back alphabetically so a caller can page through the whole corpus deterministically.
MCPツール chick_fil_a_faq
/chick-fil-a/contentReturns one page of a Chick-fil-A editorial corpus. `type` selects which: `press-room` (289 press releases), `story` (189 blog articles), `page` (147 standalone corporate pages such as hunger relief and community programmes), `legal` (28 terms, policies and promotion rules) or `downloadable-asset` (45 press-kit media entries, which carry a title and link only and never a body). Between them these are every content-bearing corpus Chick-fil-A publishes outside the menu and restaurant catalogs. Article bodies are opt-in via include_body because a single press release runs to roughly 22KB, so a default-on page of 20 would be several hundred KB; without it the endpoint returns titles, links, publish dates and excerpts.
MCPツール chick_fil_a_content
/chick-fil-a/content-taxonomyReturns one page of a content taxonomy's terms, each with its id, name, slug, parent and the number of entries carrying it. Every id is a ready-to-use `category` or `tag` filter value on GET /chick-fil-a/content, which is what makes the editorial corpora navigable rather than only pageable. `taxonomy` selects the vocabulary: `press_category` (16 terms) and `press_tag` (96) classify press releases, `story_category` (9) and `story_tag` (74) classify blog stories, `legal_category` (8) and `downloadable_asset_category` (7) classify those corpora, and `campaign` (9) is applied across several at once. Terms are ordered by name.
MCPツール chick_fil_a_content_taxonomy
関連API
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.
Chick-fil-Aのスクレイピング方法
Crawlora's Chick-fil-A endpoints return normalized public Chick-fil-A data as JSON with one API key — no Chick-fil-A account required. Chick-fil-A does not publish restaurant coordinates, menu prices, or nutrition values through this source, and every list endpoint pages alphabetically without a search term for deterministic full-corpus walks.
Call /chick-fil-a/locations for the 3,467-restaurant directory (id, slug, name, state) — search filters by name, relevance-ranked. Pass a slug to /chick-fil-a/location for that restaurant's street address, opening hours (Sundays and inactive seasonal/food-truck locations come back correctly flagged closed), cuisine description, and photo. No coordinates are published for either.
Call /chick-fil-a/menu for the 567-item catalog (name, slug, ordering deep link, taxonomy term ids) — no prices or nutrition. Call /chick-fil-a/menu-taxonomy with a taxonomy (menu_taxonomy, menu_item_type, menu_item_group, or nutrition_table_menu) to discover filter values, then /chick-fil-a/menu-item for one item's full detail with taxonomy ids resolved to names.
Call /chick-fil-a/content with a type (press-room, story, page, legal, or downloadable-asset) for that corpus — set include_body for full article text (press releases run ~22KB each, so it's opt-in). Use /chick-fil-a/content-taxonomy with a taxonomy (e.g. press_category, story_tag, campaign) to discover category and tag filter values first.
Call /chick-fil-a/faq for the 522-entry FAQ corpus across 30 categories (Chick-fil-A One membership, delivery support, sweepstakes terms, and more) — each entry carries both plain-text and original-HTML answer bodies. search relevance-ranks by question and answer text; omit it to page alphabetically.
FAQ
Call /chick-fil-a/locations for the restaurant directory, /chick-fil-a/menu for the menu catalog, /chick-fil-a/faq for customer FAQs, or /chick-fil-a/content for press releases, blog stories, and legal documents — all return structured JSON with one API key.
No. /chick-fil-a/location returns a full street address and hours but no latitude/longitude — Chick-fil-A does not publish coordinates for its restaurants through this source.
No. Neither /chick-fil-a/menu nor /chick-fil-a/menu-item publishes prices or nutrition — Chick-fil-A does not expose either through this source.
Yes — /chick-fil-a/content-taxonomy returns each vocabulary's terms (e.g. press_category, story_tag) with ready-to-use ids for the category/tag filters on /chick-fil-a/content, and /chick-fil-a/faq accepts a category filter directly using the same category ids its own entries carry.
A single press release runs to roughly 22KB of body text, so a default-on page of 20 entries would return several hundred KB. Without include_body, entries come back with titles, links, publish dates, and excerpts only.