{ "data": { "a": { "slug": "opentable", "name": "OpenTable APIs", "vendor": "OpenTable", "vendorUrl": "https://www.opentable.com", "kind": "http-api", "category": "local-bookings", "summary": "OpenTable's partner APIs let approved partners search restaurant availability and make, change and cancel reservations, for diners through the Consumer API or for restaurants' voice agents through the In-House Booking API, with OAuth 2.0 client credentials.", "url": "https://www.anchorterminal.com/tools/opentable", "markdownUrl": "https://www.anchorterminal.com/tools/opentable.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/opentable.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/opentable.json", "license": "Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation", "transports": [ "http" ], "remoteUrl": "https://platform.opentable.com", "packages": [], "auth": "oauth", "authNotes": "Partner approval required. A partner applies through OpenTable's become-a-partner form, the partnerships team reviews the application, and approved partners receive sandbox credentials and restaurant IDs in a welcome email. Tokens come from the OAuth 2.0 client credentials grant at https://oauth-pp.opentable.com (sandbox) or https://oauth.opentable.com (production), with the client ID and secret Base64-encoded in the Authorization header. The Platform Policy forbids sharing credentials and says OpenTable may require rotation. Restaurants connect a partner through an OAuth or unique-identifier onboarding flow in the Integrations Marketplace.", "pricing": "byo-plan", "pricingNotes": "No API prices are published. Use is governed by each partner's agreement with OpenTable, and the docs say new implementations may need additional contracting and certification. A sandbox is granted after approval. The change log describes a configurable OpenTable Service Fee (shown to diners as 2 per cent) that restaurants may pass on to diners on experiences, deposits and card holds (https://docs.opentable.com/).", "priceSummary": "Your plan", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the public API documentation (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.opentable.com", "capabilities": [ "booking.availability", "booking.reservations", "booking.venue", "crm.records" ], "tags": [ "hosted", "closed-source", "partner-only", "rest", "oauth", "webhooks", "sandbox", "restaurants" ], "graded": true, "anchor": { "graded": true, "score": 38.6, "grade": "E", "agentReady": false, "rank": 994, "ranked": true, "rankOf": 1076, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 5, "payments": 5, "reliability": 35, "schema": 61, "security": 33, "transparency": 42 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.", "bestFor": "Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.", "strengths": [ "Diner-side Consumer API v2 and venue-side In-House Booking API both cover availability, slot lock, booking, change and cancellation", "Booking and cancellation policy endpoints return deposits, holds and cut-off rules before a booking is made", "X-Request-Id on POST, PUT and PATCH requests makes retries safe", "Error tables name business-rule failures such as DinerHasOverlappingReservations with their HTTP codes", "A sandbox environment with its own OAuth host is granted after approval" ], "weaknesses": [ "Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials", "Rate limits are not published and come from the OpenTable representative", "No OpenAPI file, llms.txt or SDK, only a Postman collection", "The change log has one dated entry, the TLS 1.3 notice of 6 October 2025", "The Platform Policy allows API changes and suspension with or without notice and promises no support" ], "agentNotes": [ "Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes", "Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated", "Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner", "Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel", "Ask the OpenTable representative for the rate limit of each endpoint before going live" ], "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": 38.6 } ], "editorialScores": { "ergonomics": 69, "maintenance": 5, "payments": 5, "reliability": 35, "schema": 61, "security": 33, "transparency": 20 }, "provenanceScore": 64 }, "connect": { "http": "curl \"https://oauth-pp.opentable.com/api/v2/oauth/token?grant_type=client_credentials\" -H \"Authorization: Basic BASE64_CLIENT_ID_AND_SECRET\"" }, "letme": { "capability": "https://letme.dev/booking.availability", "tool": "https://letme.dev/opentable" }, "area": "everyday", "provenance": { "legalEntity": "", "domain": "opentable.com", "domainRegistered": "1999-01-17", "endpointOnVendorDomain": true, "terms": "https://www.opentable.com/legal/terms-and-conditions", "privacy": "https://www.opentable.com/legal/privacy-policy", "statusPage": "https://status.opentable.com", "changelog": "https://docs.opentable.com/", "securityTxt": "unknown", "checked": "2026-10-14", "notes": [ "The terms and privacy URLs are the ones the API documentation links. www.opentable.com timed out on every request from our network on 14 October 2026, including robots.txt, so neither page nor the legal entity was read.", "The API's own Platform Policy (last updated 20 December 2024) is published at the top of docs.opentable.com and refers to each partner's agreement with OpenTable.", "status.opentable.com is a StatusDashboard page whose components and history load by script and were not readable to our reader.", "The change log is a section of the documentation (API Reference, Change Log), not a separate page.", "security.txt could not be fetched because www.opentable.com did not answer.", "RDAP gives opentable.com a registration date of 1999-01-17." ], "score": 64 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/opentable.json", "live": { "slug": "opentable", "probe": { "target": "https://platform.opentable.com", "method": "get", "lastAt": "2026-10-14T09:42:01.177574691Z", "lastOk": true, "lastStatus": 200, "lastMs": 476, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 545, "p95ms24h": 2988, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.opentable.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:44.535821064Z" }, "updatedAt": "2026-10-14T09:42:01.177574691Z" } }, "answer": "TableCheck API scores 57.1 (C) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 6 of 7 scored categories. OpenTable APIs leads on payments \u0026 pricing.", "b": { "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" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "OpenTable", "b": "TableCheck Inc.", "name": "Vendor" }, { "a": "https://platform.opentable.com", "b": "https://api.tablecheck.com/api/", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "API key", "name": "Auth" }, { "a": "Your plan", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation", "b": "Proprietary service under the TableCheck API Terms of Service", "name": "Licence" }, { "a": "none", "b": "20", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "couldn't be read", "b": "2022-10-11", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2016-12-14", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "TableCheck API scores 57.1 (C) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 6 of 7 scored categories. OpenTable APIs leads on payments \u0026 pricing.", "question": "Which is better for AI agents, OpenTable APIs or TableCheck API?" }, { "answer": "OpenTable APIs uses an OAuth sign-in. TableCheck API needs an API key.", "question": "Do OpenTable APIs and TableCheck API need an API key?" }, { "answer": "Yes. OpenTable APIs has a hosted endpoint at https://platform.opentable.com and TableCheck API at https://api.tablecheck.com/api/.", "question": "Can an agent call OpenTable APIs and TableCheck API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 5 against 0" ], "also": null, "goodFor": "Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.", "slug": "opentable", "watchFor": "Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials" }, { "aheadOn": [ "Reliability, 80 against 35", "Schema \u0026 documentation, 77 against 61", "Security \u0026 auth, 46 against 33", "Maintenance \u0026 community, 35 against 5", "Transparency \u0026 trust, 66 against 42" ], "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" } ], "job": { "capability": "booking.availability", "name": "Booking availability" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chope-vs-opentable.json", "title": "Chope vs OpenTable APIs", "url": "https://www.anchorterminal.com/compare/chope-vs-opentable" }, { "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/eat-app-vs-opentable.json", "title": "Eat App Partner API vs OpenTable APIs", "url": "https://www.anchorterminal.com/compare/eat-app-vs-opentable" }, { "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/opentable-vs-tock.json", "title": "OpenTable APIs vs Tock", "url": "https://www.anchorterminal.com/compare/opentable-vs-tock" }, { "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/tablecheck-vs-tock.json", "title": "TableCheck API vs Tock", "url": "https://www.anchorterminal.com/compare/tablecheck-vs-tock" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-resy.json", "title": "OpenTable APIs vs Resy", "url": "https://www.anchorterminal.com/compare/opentable-vs-resy" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.json", "title": "OpenTable APIs vs SevenRooms", "url": "https://www.anchorterminal.com/compare/opentable-vs-sevenrooms" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-square-appointments.json", "title": "OpenTable APIs vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/opentable-vs-square-appointments" }, { "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/tablecheck-vs-thefork.json", "title": "TableCheck API vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/tablecheck-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" } ], "scores": [ { "by": 45, "edge": "tablecheck", "key": "reliability", "name": "Reliability", "opentable": 35, "tablecheck": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 16, "edge": "tablecheck", "key": "schema", "name": "Schema \u0026 documentation", "opentable": 61, "tablecheck": 77, "weight": 13 }, { "by": 3, "edge": "tablecheck", "key": "ergonomics", "name": "Agent ergonomics", "opentable": 69, "tablecheck": 72, "weight": 13 }, { "by": 13, "edge": "tablecheck", "key": "security", "name": "Security \u0026 auth", "opentable": 33, "tablecheck": 46, "weight": 14 }, { "by": 5, "edge": "opentable", "key": "payments", "name": "Payments \u0026 pricing", "opentable": 5, "tablecheck": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 30, "edge": "tablecheck", "key": "maintenance", "name": "Maintenance \u0026 community", "opentable": 5, "tablecheck": 35, "weight": 7 }, { "by": 24, "edge": "tablecheck", "key": "transparency", "name": "Transparency \u0026 trust", "opentable": 42, "tablecheck": 66, "weight": 7 } ], "summary": "TableCheck API scores 57.1 (C) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 6 of 7 scored categories. OpenTable APIs leads on payments \u0026 pricing. Both do booking availability.", "verdicts": { "opentable": "The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck", "json": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck.md", "slim": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck.min.md" }, "markdown": "TableCheck API scores 57.1 (C) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 6 of 7 scored categories. OpenTable APIs leads on payments \u0026 pricing. Both do booking availability.\n\n- OpenTable APIs: grade E, 38.6/100, rank #994 of 1076. Markdown https://www.anchorterminal.com/tools/opentable.md · JSON https://www.anchorterminal.com/api/v1/tools/opentable.json\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- 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### OpenTable APIs (E)\n\nGood for: Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.\n\nAhead on:\n- Payments \u0026 pricing, 5 against 0\n\nWatch for: Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials\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- Schema \u0026 documentation, 77 against 61\n- Security \u0026 auth, 46 against 33\n- Maintenance \u0026 community, 35 against 5\n- Transparency \u0026 trust, 66 against 42\n\nWatch for: Access needs an emailed application, case-by-case approval and fees quoted privately\n\n\n## Score by category\n\n| Category | Weight | OpenTable APIs | TableCheck API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 80 | TableCheck API +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 77 | TableCheck API +16 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 72 | TableCheck API +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 33 | 46 | TableCheck API +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 0 | OpenTable APIs +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 5 | 35 | TableCheck API +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 42 | 66 | TableCheck API +24 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **38.6 · E** | **57.1 · C** | |\n\n## Facts side by side\n\n| Fact | OpenTable APIs | TableCheck API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | OpenTable | TableCheck Inc. |\n| Hosted endpoint | `https://platform.opentable.com` | `https://api.tablecheck.com/api/` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | API key |\n| Pricing | Your plan | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation | Proprietary service under the TableCheck API Terms of Service |\n| Tools exposed | none | 20 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | no |\n| Terms last updated | couldn't be read | 2022-10-11 |\n| Privacy policy last updated | couldn't be read | 2016-12-14 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n\n## Verdicts\n\n**OpenTable APIs.** The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.\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## Before you call either\n\n### OpenTable APIs\n\n1. Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes\n2. Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated\n3. Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner\n4. Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel\n5. Ask the OpenTable representative for the rate limit of each endpoint before going live\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## Questions\n\n### Which is better for AI agents, OpenTable APIs or TableCheck API?\n\nTableCheck API scores 57.1 (C) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 6 of 7 scored categories. OpenTable APIs leads on payments \u0026 pricing.\n\n### Do OpenTable APIs and TableCheck API need an API key?\n\nOpenTable APIs uses an OAuth sign-in. TableCheck API needs an API key.\n\n### Can an agent call OpenTable APIs and TableCheck API without installing anything?\n\nYes. OpenTable APIs has a hosted endpoint at https://platform.opentable.com and TableCheck API at https://api.tablecheck.com/api/.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/opentable-vs-tablecheck.json, and with the fewest tokens: https://www.anchorterminal.com/compare/opentable-vs-tablecheck.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"opentable\", \"b\": \"tablecheck\"}`. From a terminal: `anchor compare opentable tablecheck`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/opentable.json and https://www.anchorterminal.com/api/v1/tools/tablecheck.json\n\n## Other comparisons with OpenTable APIs or TableCheck API\n\n- [Chope vs OpenTable APIs](https://www.anchorterminal.com/compare/chope-vs-opentable.md)\n- [Chope vs TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.md)\n- [Eat App Partner API vs OpenTable APIs](https://www.anchorterminal.com/compare/eat-app-vs-opentable.md)\n- [Eat App Partner API vs TableCheck API](https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.md)\n- [OpenTable APIs vs Tock](https://www.anchorterminal.com/compare/opentable-vs-tock.md)\n- [Resy vs TableCheck API](https://www.anchorterminal.com/compare/resy-vs-tablecheck.md)\n- [TableCheck API vs Tock](https://www.anchorterminal.com/compare/tablecheck-vs-tock.md)\n- [OpenTable APIs vs Resy](https://www.anchorterminal.com/compare/opentable-vs-resy.md)\n- [OpenTable APIs vs SevenRooms](https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.md)\n- [OpenTable APIs vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/opentable-vs-square-appointments.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- [TableCheck API vs TheFork B2B API](https://www.anchorterminal.com/compare/tablecheck-vs-thefork.md)\n- [SevenRooms vs TableCheck API](https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.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": "OpenTable APIs vs TableCheck API", "url": "" } ], "description": "TableCheck scores 57.1 (C) to OpenTable's 38.6 (E) for booking availability. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "OpenTable APIs E 38.6", "TableCheck API C 57.1", "scores" ], "h1": "OpenTable APIs vs TableCheck API", "image": "https://www.anchorterminal.com/assets/og/compare-opentable-vs-tablecheck.png", "path": "/compare/opentable-vs-tablecheck", "published": "2026-10-01", "section": "tools", "title": "OpenTable vs TableCheck for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck" }, "tokens": { "markdown": 2200, "slim": 730 }, "version": 1 }