{ "data": { "a": { "slug": "tablecheck", "name": "TableCheck API", "vendor": "TableCheck Inc.", "vendorUrl": "https://www.tablecheck.com", "kind": "http-api", "category": "local-bookings", "summary": "TableCheck is a restaurant reservation and guest management platform used mainly in Japan and Asia. Its API components cover availability, booking, CRM, POS and distribution to booking sites, with an MCP server for merchants.", "url": "https://www.anchorterminal.com/tools/tablecheck", "markdownUrl": "https://www.anchorterminal.com/tools/tablecheck.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tablecheck.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tablecheck.json", "license": "Proprietary service under the TableCheck API Terms of Service", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.tablecheck.com/api/", "packages": [], "auth": "api-key", "authNotes": "Sales-led. Email api@tablecheck.com, complete the API Portal questionnaire and accept the API terms. Each approved request gets one `secret_key` per environment in the `Authorization` header, limited to the approved components and, for aggregators, approved venues. The API team rolls keys on request. The MCP server needs the `mcp_merchant` component added to a key (https://tablecheck.atlassian.net/wiki/spaces/API/pages/44630975).", "pricing": "paid", "pricingNotes": "No public price. The access page says \"Fees may vary\" and pricing is given during the application. No free tier. Test accounts and test data are prepared on request (https://tablecheck.atlassian.net/wiki/spaces/API/pages/43909423, checked 2026-10-14).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation or the OpenAPI files read (checked 2026-10-14).", "endpoints": [] }, "toolCount": 20, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://tablecheck.atlassian.net/wiki/spaces/API/overview", "openapi": "https://api.tablecheck.com/api/booking/v1/docs", "capabilities": [ "booking.availability", "booking.reservations", "booking.venue", "booking.orders" ], "tags": [ "hosted", "closed-source", "rest", "openapi", "mcp", "sales-led", "status-page", "diner-side", "venue-side" ], "graded": true, "anchor": { "graded": true, "score": 57.1, "grade": "C", "agentReady": false, "rank": 661, "ranked": true, "rankOf": 1076, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 35, "payments": 0, "reliability": 80, "schema": 77, "security": 46, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "TableCheck publishes OpenAPI specs for availability, booking, CRM and POS components and a merchant MCP server with read-only keys, idempotent writes and personal data hidden by default. Access is by email application with case-by-case approval and unpublished fees, the MCP server is still under development, and no audit log or dated changelog was found.", "bestFor": "Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.", "strengths": [ "OpenAPI 3.0 YAML served for each component, with a written change and deprecation policy", "Separate APIs for diner-side platforms (Availability, Distribution, Web Booking) and venue-side systems (Booking, CRM, POS)", "MCP for Merchants hides guest names, phones and emails unless asked and supports read-only keys", "MCP write tools take an idempotency key and are annotated destructive", "Rate limit stated as 10,000 requests per 5 minutes per component" ], "weaknesses": [ "Access needs an emailed application, case-by-case approval and fees quoted privately", "MCP for Merchants is under development and its tools may change without a version bump", "REST POST /reservations has no idempotency key", "Keys are issued and rolled only by the API team, with no audit log found", "Booking v1 needs per-venue approval for aggregators, and only a production environment exists by default" ], "agentNotes": [ "Decide which side you act for. Distribution and Web Booking serve diner-facing platforms, while Booking, CRM, POS and the MCP serve the venue", "Ask the operator for a read-only key before using the MCP, as TableCheck recommends, and avoid cancellations through it", "Call `hold_table` (MCP) or POST /blockages (REST) before booking, since availability is a snapshot and a blockage expires in 5 minutes", "Send dates as YYYY-MM-DD and convert the UTC times returned to the venue's time zone from `list_shops`", "Stay under 10,000 requests per 5 minutes per component and wait for the next window after a 429" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.1 } ], "editorialScores": { "ergonomics": 72, "maintenance": 35, "payments": 0, "reliability": 80, "schema": 77, "security": 46, "transparency": 45 }, "provenanceScore": 86 }, "connect": { "claudeCode": "claude mcp add --transport http tablecheck \\\n https://api.staging-qa.tablecheck.com/api/mcp_merchant/v1 \\\n --header \"Authorization: Bearer $TABLECHECK_API_KEY\"", "config": { "mcpServers": { "tablecheck": { "headers": { "Authorization": "Bearer ${TABLECHECK_API_KEY}" }, "type": "http", "url": "https://api.staging-qa.tablecheck.com/api/mcp_merchant/v1" } } } }, "letme": { "capability": "https://letme.dev/booking.availability", "tool": "https://letme.dev/tablecheck" }, "area": "everyday", "provenance": { "legalEntity": "TableCheck Inc.", "domain": "tablecheck.com", "domainRegistered": "1998-07-01", "endpointOnVendorDomain": true, "terms": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/61571353/TableCheck+API+Terms+of+Service", "privacy": "https://www.tablecheck.com/en/policy/privacy", "statusPage": "https://tablecheck.statuspage.io", "changelog": "https://tablecheck.atlassian.net/wiki/spaces/API/pages/2603253889", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The API Terms of Service (enacted 10 December 2018) are with TableCheck, Inc. outside Mainland China and its designated entity inside it.", "The privacy policy (revised 14 September 2026) names TableCheck Inc., KR Ginza II 5F, 2-15-2 Ginza, Chuo-ku, Tokyo.", "The API documentation is hosted on tablecheck.atlassian.net. api.tablecheck.com redirects there.", "www.tablecheck.com/.well-known/security.txt returns an HTML page, read as no security.txt.", "RDAP gives a registration date of 1998-07-01 for tablecheck.com." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tablecheck.json", "live": { "slug": "tablecheck", "probe": { "target": "https://api.tablecheck.com/api/", "method": "get", "lastAt": "2026-10-14T09:42:09.492395571Z", "lastOk": true, "lastStatus": 200, "lastMs": 717, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 711, "p95ms24h": 871, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://tablecheck.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:43.550229393Z" }, "updatedAt": "2026-10-14T09:42:09.492395571Z" } }, "answer": "TableCheck API scores 57.1 (C) on agent readiness against TheFork B2B API's 43.6 (E), and leads in 5 of 7 scored categories. TheFork B2B API leads on schema \u0026 documentation and payments \u0026 pricing.", "b": { "slug": "thefork", "name": "TheFork B2B API", "vendor": "TheFork (La Fourchette SAS)", "vendorUrl": "https://www.thefork.com", "kind": "http-api", "category": "local-bookings", "summary": "TheFork's B2B API lets restaurants and their software partners, such as CRM vendors and AI phone agents, read availability and create, change and cancel reservations in TheFork Manager, with webhooks, reviews and customer data.", "url": "https://www.anchorterminal.com/tools/thefork", "markdownUrl": "https://www.anchorterminal.com/tools/thefork.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/thefork.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/thefork.json", "license": "Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork", "transports": [ "http" ], "remoteUrl": "https://api.thefork.io/manager", "packages": [], "auth": "oauth", "authNotes": "Partner approval required. Credentials are requested from the integrations team at integrations@thefork.com with a company name and use case. TheFork sends a client_id and client_secret through a secure channel, and the client exchanges them at https://auth.thefork.io/oauth/token (OAuth 2.0 client credentials, audience https://api.thefork.io) for a Bearer token that lasts 8,600 seconds. Nine scopes limit each client, from full access (tfm-restaurant) to read-only availability. restaurantUuid and groupUuid values for each restaurant come from TheFork, as no endpoint lists them.", "pricing": "byo-plan", "pricingNotes": "No API prices are published. Access follows a partnership with TheFork, and the rate limit is set by contract. The API terms mention test data for pre-launch testing. No sandbox host or self-serve tier is documented (https://docs.thefork.io/getting-started).", "priceSummary": "Your plan", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer portal, llms.txt or OpenAPI schema (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.thefork.io/B2B-API/introduction", "llmsTxt": "https://docs.thefork.io/B2B-API/llms.txt", "openapi": "https://api.thefork.io/manager/openapi.json", "capabilities": [ "booking.reservations", "booking.availability", "booking.venue", "crm.records", "events.webhooks-send" ], "tags": [ "hosted", "closed-source", "partner-only", "rest", "oauth", "openapi", "llms-txt", "webhooks", "eu", "restaurants" ], "graded": true, "anchor": { "graded": true, "score": 43.6, "grade": "E", "agentReady": false, "rank": 951, "ranked": true, "rankOf": 1076, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 15, "payments": 5, "reliability": 35, "schema": 87, "security": 42, "transparency": 47 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices.", "bestFor": "CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.", "strengths": [ "OpenAPI 3.1 schema generated from the deployed code, with 19 operations, enums, examples and error responses", "llms.txt for the B2B API covers scopes per endpoint, time zones, reservation statuses and error formats", "Nine OAuth scopes, including read-only availability and a separate scope for unrestricted bookings that is off by default", "Business error codes such as NO_AVAILABILITY, DOUBLE_BOOKING and RESERVATION_NOT_FOUND", "Written versioning policy with 6 months of support for the previous version" ], "weaknesses": [ "Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants", "Credentials come from the integrations team by email after approval, with no self-serve route", "Timeslots that need a payment guarantee cannot be booked through the API", "The status page at status.thefork.io redirects to a private Rootly page that needs a sign-in", "No changelog, idempotency key or published production rate limit" ], "agentNotes": [ "Read hasPaymentGuaranteeRequirement in the timeslots response before booking, since the API cannot take a card", "Check the status field after creating a reservation and treat REQUESTED as unconfirmed", "Send the timeslot datetime unchanged as mealDate, because times are the restaurant's local time", "Check for an existing reservation before retrying a failed POST, as no idempotency key exists and 409 signals DOUBLE_BOOKING", "Cache the access token for its 8,600 seconds and do not request a new one while it is valid" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.6 } ], "editorialScores": { "ergonomics": 56, "maintenance": 15, "payments": 5, "reliability": 35, "schema": 87, "security": 42, "transparency": 33 }, "provenanceScore": 60 }, "connect": { "http": "curl -X POST https://auth.thefork.io/oauth/token -H 'Content-Type: application/x-www-form-urlencoded' -d 'audience=https://api.thefork.io\u0026grant_type=client_credentials\u0026client_id=CLIENT_ID\u0026client_secret=CLIENT_SECRET'" }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/thefork" }, "area": "everyday", "provenance": { "legalEntity": "La Fourchette SAS", "domain": "thefork.io", "domainRegistered": "2016-05-30", "endpointOnVendorDomain": true, "terms": "https://docs.thefork.io/pdf/LaFourchette-Partners-API-Licence-2.pdf", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The developer portal footer links the TheFork Partners API Terms of Use, a PDF naming La Fourchette SAS, 70 rue Saint Lazare, Paris, company number 494 447 949, where no core agreement exists.", "www.thefork.com answered with a bot check (403), so its privacy policy and terms were not read and no privacy URL is recorded.", "status.thefork.io redirects to a private Rootly status page that needs a sign-in, so no public status page is recorded.", "www.thefork.com/.well-known/security.txt returns 404 and docs.thefork.io/.well-known/security.txt returns 403.", "No changelog was found. docs.thefork.io/changelog returns 403.", "RDAP gives thefork.io a registration date of 2016-05-30 and thefork.com 1998-11-04." ], "score": 60 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/thefork.json", "live": { "slug": "thefork", "probe": { "target": "https://api.thefork.io/manager", "method": "get", "lastAt": "2026-10-14T09:42:10.255461561Z", "lastOk": true, "lastStatus": 404, "lastMs": 57, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 56, "p95ms24h": 119, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "updatedAt": "2026-10-14T09:42:10.255461561Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "TableCheck Inc.", "b": "TheFork (La Fourchette SAS)", "name": "Vendor" }, { "a": "https://api.tablecheck.com/api/", "b": "https://api.thefork.io/manager", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Your plan", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the TableCheck API Terms of Service", "b": "Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork", "name": "Licence" }, { "a": "20", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2022-10-11", "b": "", "name": "Terms last updated" }, { "a": "2016-12-14", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "TableCheck API scores 57.1 (C) on agent readiness against TheFork B2B API's 43.6 (E), and leads in 5 of 7 scored categories. TheFork B2B API leads on schema \u0026 documentation and payments \u0026 pricing.", "question": "Which is better for AI agents, TableCheck API or TheFork B2B API?" }, { "answer": "TableCheck API needs an API key. TheFork B2B API uses an OAuth sign-in.", "question": "Do TableCheck API and TheFork B2B API need an API key?" }, { "answer": "Yes. TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/ and TheFork B2B API at https://api.thefork.io/manager.", "question": "Can an agent call TableCheck API and TheFork B2B API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 35", "Agent ergonomics, 72 against 56", "Maintenance \u0026 community, 35 against 15", "Transparency \u0026 trust, 66 against 47" ], "also": null, "goodFor": "Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.", "slug": "tablecheck", "watchFor": "Access needs an emailed application, case-by-case approval and fees quoted privately" }, { "aheadOn": [ "Schema \u0026 documentation, 87 against 77", "Payments \u0026 pricing, 5 against 0" ], "also": null, "goodFor": "CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.", "slug": "thefork", "watchFor": "Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants" } ], "job": { "capability": "booking.availability", "name": "Booking availability" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chope-vs-tablecheck.json", "title": "Chope vs TableCheck API", "url": "https://www.anchorterminal.com/compare/chope-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/chope-vs-thefork.json", "title": "Chope vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/chope-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.json", "title": "Eat App Partner API vs TableCheck API", "url": "https://www.anchorterminal.com/compare/eat-app-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-thefork.json", "title": "Eat App Partner API vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/eat-app-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-tablecheck.json", "title": "Resy vs TableCheck API", "url": "https://www.anchorterminal.com/compare/resy-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-thefork.json", "title": "Resy vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/resy-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/tablecheck-vs-tock.json", "title": "TableCheck API vs Tock", "url": "https://www.anchorterminal.com/compare/tablecheck-vs-tock" }, { "json": "https://www.anchorterminal.com/compare/thefork-vs-tock.json", "title": "TheFork B2B API vs Tock", "url": "https://www.anchorterminal.com/compare/thefork-vs-tock" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck.json", "title": "OpenTable APIs vs TableCheck API", "url": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-thefork.json", "title": "OpenTable APIs vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/opentable-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/square-appointments-vs-tablecheck.json", "title": "Square Appointments (Bookings API) vs TableCheck API", "url": "https://www.anchorterminal.com/compare/square-appointments-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/square-appointments-vs-thefork.json", "title": "Square Appointments (Bookings API) vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/square-appointments-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.json", "title": "SevenRooms vs TableCheck API", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.json", "title": "SevenRooms vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork" } ], "scores": [ { "by": 45, "edge": "tablecheck", "key": "reliability", "name": "Reliability", "tablecheck": 80, "thefork": 35, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "edge": "thefork", "key": "schema", "name": "Schema \u0026 documentation", "tablecheck": 77, "thefork": 87, "weight": 13 }, { "by": 16, "edge": "tablecheck", "key": "ergonomics", "name": "Agent ergonomics", "tablecheck": 72, "thefork": 56, "weight": 13 }, { "by": 4, "edge": "tablecheck", "key": "security", "name": "Security \u0026 auth", "tablecheck": 46, "thefork": 42, "weight": 14 }, { "by": 5, "edge": "thefork", "key": "payments", "name": "Payments \u0026 pricing", "tablecheck": 0, "thefork": 5, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 20, "edge": "tablecheck", "key": "maintenance", "name": "Maintenance \u0026 community", "tablecheck": 35, "thefork": 15, "weight": 7 }, { "by": 19, "edge": "tablecheck", "key": "transparency", "name": "Transparency \u0026 trust", "tablecheck": 66, "thefork": 47, "weight": 7 } ], "summary": "TableCheck API scores 57.1 (C) on agent readiness against TheFork B2B API's 43.6 (E), and leads in 5 of 7 scored categories. TheFork B2B API leads on schema \u0026 documentation and payments \u0026 pricing. Both do booking availability.", "verdicts": { "tablecheck": "TableCheck publishes OpenAPI specs for availability, booking, CRM and POS components and a merchant MCP server with read-only keys, idempotent writes and personal data hidden by default. Access is by email application with case-by-case approval and unpublished fees, the MCP server is still under development, and no audit log or dated changelog was found.", "thefork": "A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/tablecheck-vs-thefork", "json": "https://www.anchorterminal.com/compare/tablecheck-vs-thefork.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/tablecheck-vs-thefork.md", "slim": "https://www.anchorterminal.com/compare/tablecheck-vs-thefork.min.md" }, "markdown": "TableCheck API scores 57.1 (C) on agent readiness against TheFork B2B API's 43.6 (E), and leads in 5 of 7 scored categories. TheFork B2B API leads on schema \u0026 documentation and payments \u0026 pricing. Both do booking availability.\n\n- TableCheck API: grade C, 57.1/100, rank #661 of 1076. Markdown https://www.anchorterminal.com/tools/tablecheck.md · JSON https://www.anchorterminal.com/api/v1/tools/tablecheck.json\n- TheFork B2B API: grade E, 43.6/100, rank #951 of 1076. Markdown https://www.anchorterminal.com/tools/thefork.md · JSON https://www.anchorterminal.com/api/v1/tools/thefork.json\n- Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md\n- All 36 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md\n\n## Which one, for what\n\n### TableCheck API (C)\n\nGood for: Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.\n\nAhead on:\n- Reliability, 80 against 35\n- Agent ergonomics, 72 against 56\n- Maintenance \u0026 community, 35 against 15\n- Transparency \u0026 trust, 66 against 47\n\nWatch for: Access needs an emailed application, case-by-case approval and fees quoted privately\n\n### TheFork B2B API (E)\n\nGood for: CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.\n\nAhead on:\n- Schema \u0026 documentation, 87 against 77\n- Payments \u0026 pricing, 5 against 0\n\nWatch for: Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants\n\n\n## Score by category\n\n| Category | Weight | TableCheck API | TheFork B2B API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 35 | TableCheck API +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 87 | TheFork B2B API +10 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 56 | TableCheck API +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 42 | TableCheck API +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 5 | TheFork B2B API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 35 | 15 | TableCheck API +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 47 | TableCheck API +19 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.1 · C** | **43.6 · E** | |\n\n## Facts side by side\n\n| Fact | TableCheck API | TheFork B2B API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | TableCheck Inc. | TheFork (La Fourchette SAS) |\n| Hosted endpoint | `https://api.tablecheck.com/api/` | `https://api.thefork.io/manager` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Paid | Your plan |\n| x402 | no | no |\n| Licence | Proprietary service under the TableCheck API Terms of Service | Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork |\n| Tools exposed | 20 | none |\n| Read-only variant documented | yes | yes |\n| llms.txt | no | yes |\n| Terms last updated | 2022-10-11 | |\n| Privacy policy last updated | 2016-12-14 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\n\n## Verdicts\n\n**TableCheck API.** TableCheck publishes OpenAPI specs for availability, booking, CRM and POS components and a merchant MCP server with read-only keys, idempotent writes and personal data hidden by default. Access is by email application with case-by-case approval and unpublished fees, the MCP server is still under development, and no audit log or dated changelog was found.\n\n**TheFork B2B API.** A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices.\n\n## Before you call either\n\n### TableCheck API\n\n1. Decide which side you act for. Distribution and Web Booking serve diner-facing platforms, while Booking, CRM, POS and the MCP serve the venue\n2. Ask the operator for a read-only key before using the MCP, as TableCheck recommends, and avoid cancellations through it\n3. Call `hold_table` (MCP) or POST /blockages (REST) before booking, since availability is a snapshot and a blockage expires in 5 minutes\n4. Send dates as YYYY-MM-DD and convert the UTC times returned to the venue's time zone from `list_shops`\n5. Stay under 10,000 requests per 5 minutes per component and wait for the next window after a 429\n\n### TheFork B2B API\n\n1. Read hasPaymentGuaranteeRequirement in the timeslots response before booking, since the API cannot take a card\n2. Check the status field after creating a reservation and treat REQUESTED as unconfirmed\n3. Send the timeslot datetime unchanged as mealDate, because times are the restaurant's local time\n4. Check for an existing reservation before retrying a failed POST, as no idempotency key exists and 409 signals DOUBLE_BOOKING\n5. Cache the access token for its 8,600 seconds and do not request a new one while it is valid\n\n## Questions\n\n### Which is better for AI agents, TableCheck API or TheFork B2B API?\n\nTableCheck API scores 57.1 (C) on agent readiness against TheFork B2B API's 43.6 (E), and leads in 5 of 7 scored categories. TheFork B2B API leads on schema \u0026 documentation and payments \u0026 pricing.\n\n### Do TableCheck API and TheFork B2B API need an API key?\n\nTableCheck API needs an API key. TheFork B2B API uses an OAuth sign-in.\n\n### Can an agent call TableCheck API and TheFork B2B API without installing anything?\n\nYes. TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/ and TheFork B2B API at https://api.thefork.io/manager.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/tablecheck-vs-thefork.json, and with the fewest tokens: https://www.anchorterminal.com/compare/tablecheck-vs-thefork.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"tablecheck\", \"b\": \"thefork\"}`. From a terminal: `anchor compare tablecheck thefork`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/tablecheck.json and https://www.anchorterminal.com/api/v1/tools/thefork.json\n\n## Other comparisons with TableCheck API or TheFork B2B API\n\n- [Chope vs TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.md)\n- [Chope vs TheFork B2B API](https://www.anchorterminal.com/compare/chope-vs-thefork.md)\n- [Eat App Partner API vs TableCheck API](https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.md)\n- [Eat App Partner API vs TheFork B2B API](https://www.anchorterminal.com/compare/eat-app-vs-thefork.md)\n- [Resy vs TableCheck API](https://www.anchorterminal.com/compare/resy-vs-tablecheck.md)\n- [Resy vs TheFork B2B API](https://www.anchorterminal.com/compare/resy-vs-thefork.md)\n- [TableCheck API vs Tock](https://www.anchorterminal.com/compare/tablecheck-vs-tock.md)\n- [TheFork B2B API vs Tock](https://www.anchorterminal.com/compare/thefork-vs-tock.md)\n- [OpenTable APIs vs TableCheck API](https://www.anchorterminal.com/compare/opentable-vs-tablecheck.md)\n- [OpenTable APIs vs TheFork B2B API](https://www.anchorterminal.com/compare/opentable-vs-thefork.md)\n- [Square Appointments (Bookings API) vs TableCheck API](https://www.anchorterminal.com/compare/square-appointments-vs-tablecheck.md)\n- [Square Appointments (Bookings API) vs TheFork B2B API](https://www.anchorterminal.com/compare/square-appointments-vs-thefork.md)\n- [SevenRooms vs TableCheck API](https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.md)\n- [SevenRooms vs TheFork B2B API](https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "TableCheck API vs TheFork B2B API", "url": "" } ], "description": "TableCheck scores 57.1 (C) to TheFork B2B's 43.6 (E) for booking availability. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "TableCheck API C 57.1", "TheFork B2B API E 43.6", "scores" ], "h1": "TableCheck API vs TheFork B2B API", "image": "https://www.anchorterminal.com/assets/og/compare-tablecheck-vs-thefork.png", "path": "/compare/tablecheck-vs-thefork", "published": "2026-10-01", "section": "tools", "title": "TableCheck vs TheFork B2B for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/tablecheck-vs-thefork" }, "tokens": { "markdown": 2200, "slim": 680 }, "version": 1 }