{ "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 Tock's 12.4 (F), and leads in 6 of 7 scored categories.", "b": { "slug": "tock", "name": "Tock", "vendor": "Tock (American Express)", "vendorUrl": "https://www.exploretock.com", "kind": "platform", "category": "local-bookings", "summary": "Tock is a reservation and experience booking platform for restaurants, wineries and other venues, owned by American Express and now part of the Resy network. Venues run it through the Tock Dashboard, and diners book on exploretock.com and Resy.", "url": "https://www.anchorterminal.com/tools/tock", "markdownUrl": "https://www.anchorterminal.com/tools/tock.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tock.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tock.json", "license": "Proprietary service under the Tock Terms of Use (effective 12 February 2026) and merchant terms", "transports": [], "packages": [], "auth": "api-key", "authNotes": "No public agent access. api.exploretock.com publishes data models for reservation exports, but its docs index reads \"Docs coming soon\" and no endpoints, base URL or key request process are published there.", "pricing": "paid", "pricingNotes": "No prices were read. The Tock home page answered 403 to our reader, and no pricing page was reached. Venue terms are in the Tock Merchant Terms of Service (https://www.exploretock.com/merchant-terms).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on api.exploretock.com or the Tock terms (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://api.exploretock.com/docs/latest/reservation.html", "capabilities": [ "booking.reservations", "booking.venue" ], "tags": [ "not-for-agents", "sales-led", "hosted", "closed-source", "partner-only", "restaurants" ], "graded": true, "anchor": { "graded": true, "score": 12.4, "grade": "F", "agentReady": false, "rank": 1062, "ranked": true, "rankOf": 1076, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 0, "maintenance": 23, "payments": 0, "reliability": 25, "schema": 5, "security": 0, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-14" }, "negative": 0, "verdict": "Tock takes reservations and experience bookings for restaurants and wineries and now feeds its venues into Resy. There is no public API or MCP server an outside agent can call today. api.exploretock.com publishes reservation data models without endpoints, and the Terms of Use forbid automated access to the site.", "bestFor": "Restaurants and wineries taking reservations and experience bookings, and for diners booking in person.", "strengths": [ "Reservation data model published with a Swagger 2.0 file of 33 definitions", "Terms of Use (February 2026) and privacy policy (November 2025) are dated and name Tock LLC", "Venues also reach diners through the Resy app since 11 August 2026" ], "weaknesses": [ "No public API or MCP server an outside agent can call. The docs index reads \"Docs coming soon\"", "The Terms of Use forbid robots, scripts and automated systems on the site", "No prices could be read, and the home page answered 403 to our reader", "No security.txt or disclosure policy found" ], "agentNotes": [ "Don't plan to call Tock from another agent. Hand the booking to the person on exploretock.com or in the Resy app", "Do not script the Tock website, which the Terms of Use forbid. A venue wanting data should ask Tock through its dashboard account" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 12.4 } ], "editorialScores": { "ergonomics": 0, "maintenance": 23, "payments": 0, "reliability": 25, "schema": 5, "security": 0, "transparency": 33 }, "provenanceScore": 71 }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/tock" }, "area": "everyday", "provenance": { "legalEntity": "Tock LLC", "domain": "exploretock.com", "domainRegistered": "2017-03-22", "endpointOnVendorDomain": true, "terms": "https://www.exploretock.com/terms", "privacy": "https://www.exploretock.com/privacy", "statusPage": "https://status.exploretock.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The Terms of Use (effective 12 February 2026) and privacy policy (effective 24 November 2025) name Tock LLC and say Tock is owned by American Express.", "www.exploretock.com/robots.txt and the home page answered 403. The terms, privacy and merchant terms pages answered 200.", "www.exploretock.com/.well-known/security.txt returns 404.", "status.exploretock.com loads by script and showed no components or history to our reader.", "RDAP gives exploretock.com a registration date of 2017-03-22." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tock.json", "live": { "slug": "tock", "vendorStatus": { "page": "https://status.exploretock.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:54:01.394581552Z" }, "updatedAt": "2026-10-14T08:54:01.394581552Z" } }, "facts": [ { "a": "HTTP API", "b": "Platform", "name": "Kind" }, { "a": "TableCheck Inc.", "b": "Tock (American Express)", "name": "Vendor" }, { "a": "https://api.tablecheck.com/api/", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the TableCheck API Terms of Service", "b": "Proprietary service under the Tock Terms of Use (effective 12 February 2026) and merchant terms", "name": "Licence" }, { "a": "20", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2022-10-11", "b": "2026-02-12", "name": "Terms last updated" }, { "a": "2016-12-14", "b": "2025-11-24", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "TableCheck API scores 57.1 (C) on agent readiness against Tock's 12.4 (F), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, TableCheck API or Tock?" }, { "answer": "TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/. No hosted endpoint is listed for Tock.", "question": "Can an agent call TableCheck API and Tock without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 25", "Schema \u0026 documentation, 77 against 5", "Agent ergonomics, 72 against 0", "Security \u0026 auth, 46 against 0", "Maintenance \u0026 community, 35 against 23", "Transparency \u0026 trust, 66 against 52" ], "also": [ "A hosted endpoint, with nothing to install" ], "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": null, "also": null, "goodFor": "Restaurants and wineries taking reservations and experience bookings, and for diners booking in person.", "slug": "tock", "watchFor": "No public API or MCP server an outside agent can call. The docs index reads \"Docs coming soon\"" } ], "job": { "capability": "booking.reservations", "name": "Restaurant reservations" }, "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-tock.json", "title": "Chope vs Tock", "url": "https://www.anchorterminal.com/compare/chope-vs-tock" }, { "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-tock.json", "title": "Eat App Partner API vs Tock", "url": "https://www.anchorterminal.com/compare/eat-app-vs-tock" }, { "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/resy-vs-tock.json", "title": "Resy vs Tock", "url": "https://www.anchorterminal.com/compare/resy-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/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" }, { "json": "https://www.anchorterminal.com/compare/sevenrooms-vs-tock.json", "title": "SevenRooms vs Tock", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-tock" }, { "json": "https://www.anchorterminal.com/compare/square-appointments-vs-tock.json", "title": "Square Appointments (Bookings API) vs Tock", "url": "https://www.anchorterminal.com/compare/square-appointments-vs-tock" } ], "scores": [ { "by": 55, "edge": "tablecheck", "key": "reliability", "name": "Reliability", "tablecheck": 80, "tock": 25, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 72, "edge": "tablecheck", "key": "schema", "name": "Schema \u0026 documentation", "tablecheck": 77, "tock": 5, "weight": 13 }, { "by": 72, "edge": "tablecheck", "key": "ergonomics", "name": "Agent ergonomics", "tablecheck": 72, "tock": 0, "weight": 13 }, { "by": 46, "edge": "tablecheck", "key": "security", "name": "Security \u0026 auth", "tablecheck": 46, "tock": 0, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "tablecheck": 0, "tock": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "tablecheck", "key": "maintenance", "name": "Maintenance \u0026 community", "tablecheck": 35, "tock": 23, "weight": 7 }, { "by": 14, "edge": "tablecheck", "key": "transparency", "name": "Transparency \u0026 trust", "tablecheck": 66, "tock": 52, "weight": 7 } ], "summary": "TableCheck API scores 57.1 (C) on agent readiness against Tock's 12.4 (F), and leads in 6 of 7 scored categories. Both do restaurant reservations.", "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.", "tock": "Tock takes reservations and experience bookings for restaurants and wineries and now feeds its venues into Resy. There is no public API or MCP server an outside agent can call today. api.exploretock.com publishes reservation data models without endpoints, and the Terms of Use forbid automated access to the site." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/tablecheck-vs-tock", "json": "https://www.anchorterminal.com/compare/tablecheck-vs-tock.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/tablecheck-vs-tock.md", "slim": "https://www.anchorterminal.com/compare/tablecheck-vs-tock.min.md" }, "markdown": "TableCheck API scores 57.1 (C) on agent readiness against Tock's 12.4 (F), and leads in 6 of 7 scored categories. Both do restaurant reservations.\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- Tock: grade F, 12.4/100, rank #1062 of 1076. Markdown https://www.anchorterminal.com/tools/tock.md · JSON https://www.anchorterminal.com/api/v1/tools/tock.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 25\n- Schema \u0026 documentation, 77 against 5\n- Agent ergonomics, 72 against 0\n- Security \u0026 auth, 46 against 0\n- Maintenance \u0026 community, 35 against 23\n- Transparency \u0026 trust, 66 against 52\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Access needs an emailed application, case-by-case approval and fees quoted privately\n\n### Tock (F)\n\nGood for: Restaurants and wineries taking reservations and experience bookings, and for diners booking in person.\n\nWatch for: No public API or MCP server an outside agent can call. The docs index reads \"Docs coming soon\"\n\n\n## Score by category\n\n| Category | Weight | TableCheck API | Tock | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 25 | TableCheck API +55 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 5 | TableCheck API +72 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 0 | TableCheck API +72 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 0 | TableCheck API +46 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 0 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 35 | 23 | TableCheck API +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 52 | TableCheck API +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.1 · C** | **12.4 · F** | |\n\n## Facts side by side\n\n| Fact | TableCheck API | Tock |\n| --- | --- | --- |\n| Kind | HTTP API | Platform |\n| Vendor | TableCheck Inc. | Tock (American Express) |\n| Hosted endpoint | `https://api.tablecheck.com/api/` | no (local only) |\n| Transports | HTTP, Streamable HTTP | |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the TableCheck API Terms of Service | Proprietary service under the Tock Terms of Use (effective 12 February 2026) and merchant terms |\n| Tools exposed | 20 | none |\n| Read-only variant documented | yes | no |\n| llms.txt | no | no |\n| Terms last updated | 2022-10-11 | 2026-02-12 |\n| Privacy policy last updated | 2016-12-14 | 2025-11-24 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\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**Tock.** Tock takes reservations and experience bookings for restaurants and wineries and now feeds its venues into Resy. There is no public API or MCP server an outside agent can call today. api.exploretock.com publishes reservation data models without endpoints, and the Terms of Use forbid automated access to the site.\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### Tock\n\n1. Don't plan to call Tock from another agent. Hand the booking to the person on exploretock.com or in the Resy app\n2. Do not script the Tock website, which the Terms of Use forbid. A venue wanting data should ask Tock through its dashboard account\n\n## Questions\n\n### Which is better for AI agents, TableCheck API or Tock?\n\nTableCheck API scores 57.1 (C) on agent readiness against Tock's 12.4 (F), and leads in 6 of 7 scored categories.\n\n### Can an agent call TableCheck API and Tock without installing anything?\n\nTableCheck API has a hosted endpoint at https://api.tablecheck.com/api/. No hosted endpoint is listed for Tock.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/tablecheck-vs-tock.json, and with the fewest tokens: https://www.anchorterminal.com/compare/tablecheck-vs-tock.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"tablecheck\", \"b\": \"tock\"}`. From a terminal: `anchor compare tablecheck tock`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/tablecheck.json and https://www.anchorterminal.com/api/v1/tools/tock.json\n\n## Other comparisons with TableCheck API or Tock\n\n- [Chope vs TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.md)\n- [Chope vs Tock](https://www.anchorterminal.com/compare/chope-vs-tock.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 Tock](https://www.anchorterminal.com/compare/eat-app-vs-tock.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- [Resy vs Tock](https://www.anchorterminal.com/compare/resy-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- [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- [SevenRooms vs Tock](https://www.anchorterminal.com/compare/sevenrooms-vs-tock.md)\n- [Square Appointments (Bookings API) vs Tock](https://www.anchorterminal.com/compare/square-appointments-vs-tock.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 Tock", "url": "" } ], "description": "TableCheck scores 57.1 (C) to Tock's 12.4 (F) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "TableCheck API C 57.1", "Tock F 12.4", "scores" ], "h1": "TableCheck API vs Tock", "image": "https://www.anchorterminal.com/assets/og/compare-tablecheck-vs-tock.png", "path": "/compare/tablecheck-vs-tock", "published": "2026-10-01", "section": "tools", "title": "TableCheck vs Tock for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/tablecheck-vs-tock" }, "tokens": { "markdown": 2000, "slim": 630 }, "version": 1 }