{ "data": { "a": { "slug": "chope", "name": "Chope", "vendor": "The Chope Group Pte Ltd", "vendorUrl": "https://www.chope.co", "kind": "platform", "category": "local-bookings", "summary": "Chope is a restaurant reservation website and app for diners in Singapore, Bangkok, Phuket, Jakarta and Bali, owned by Grab. Diners search restaurants, book tables and pay deposits where a restaurant asks for one.", "url": "https://www.anchorterminal.com/tools/chope", "markdownUrl": "https://www.anchorterminal.com/tools/chope.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/chope.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/chope.json", "license": "Proprietary service under Chope's Terms \u0026 Conditions", "transports": [], "packages": [], "auth": "mixed", "authNotes": "No developer access. Diners sign up with an email or Facebook, or book as a guest and manage the booking with a confirmation code (https://www.chope.co/singapore-restaurants/pages/dinerfaq).", "pricing": "free", "pricingNotes": "Free for diners, and the app is free on the App Store. Restaurants may ask for a deposit for set menus, large groups, particular days or occasions (https://www.chope.co/singapore-restaurants/pages/dinerfaq, checked 2026-10-14).", "priceSummary": "Free", "where": "local", "x402": { "level": "no", "evidence": "No API, so no x402, MPP or L402 (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "capabilities": [ "booking.reservations", "booking.availability" ], "tags": [ "hosted", "closed-source", "not-for-agents", "ios", "android", "free", "diner-side" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 13.3, "grade": "F", "agentReady": false, "rank": 1057, "ranked": true, "rankOf": 1076, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 0, "maintenance": 34, "payments": 30, "reliability": 15, "schema": 0, "security": 0, "transparency": 41 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Chope is a diner-facing restaurant booking site and app in Singapore, Bangkok, Phuket, Jakarta and Bali, owned by Grab, with free bookings and app releases in September 2026. No public API or MCP server lets an outside agent search or book, and restaurant integrations run through partners such as TableCheck and SevenRooms by arrangement.", "bestFor": "A person booking restaurants in Singapore, Thailand and Indonesia.", "strengths": [ "Free for diners, with deposits set by each restaurant and explained in the diner FAQ", "iOS releases on 15 and 30 September 2026", "Dated notices for product changes, such as the end of Chope-Dollars from 15 October 2026" ], "weaknesses": [ "No public API or MCP server that an outside agent can call", "The Terms \u0026 Conditions forbid spidering, scraping or mirroring without written permission", "No status page, security.txt or named processors, apart from Grab", "The privacy notice gives no retention periods" ], "agentNotes": [ "Don't plan to call Chope from another agent. Hand the booking to the person, who can use the Chope site, the app or Grab Dine Out", "For a restaurant on Chope that also uses TableCheck or SevenRooms, check whether that platform's API covers the venue", "Tell the person that some restaurants ask for a deposit, which depends on the restaurant, day and party size" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 13.3 } ], "editorialScores": { "ergonomics": 0, "maintenance": 34, "payments": 30, "reliability": 15, "schema": 0, "security": 0, "transparency": 43 }, "provenanceScore": 39 }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/chope" }, "area": "everyday", "provenance": { "legalEntity": "The Chope Group Pte Ltd", "domain": "chope.co", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "https://www.chope.co/singapore-restaurants/tc", "privacy": "https://www.chope.co/singapore-restaurants/tc", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The Terms \u0026 Conditions (last updated 11 September 2023) and the privacy notice (last updated 6 March 2025) are on one page with tabs.", "www.chope.co/.well-known/security.txt returns 404, and status.chope.co redirects to the home page.", "The RDAP registration date for chope.co was not returned." ], "score": 39 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/chope.json" }, "answer": "TableCheck API scores 57.1 (C) on agent readiness against Chope's 13.3 (F), and leads in 6 of 7 scored categories. Chope 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": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "The Chope Group Pte Ltd", "b": "TableCheck Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.tablecheck.com/api/", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Free", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Chope's Terms \u0026 Conditions", "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": "2026-09-30", "b": "none", "name": "Last release" }, { "a": "2023-09-11", "b": "2022-10-11", "name": "Terms last updated" }, { "a": "2023-09-11", "b": "2016-12-14", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "TableCheck API scores 57.1 (C) on agent readiness against Chope's 13.3 (F), and leads in 6 of 7 scored categories. Chope leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Chope or TableCheck API?" }, { "answer": "No hosted endpoint is listed for Chope. TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/.", "question": "Can an agent call Chope and TableCheck API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 0" ], "also": null, "goodFor": "A person booking restaurants in Singapore, Thailand and Indonesia.", "slug": "chope", "watchFor": "No public API or MCP server that an outside agent can call" }, { "aheadOn": [ "Reliability, 80 against 15", "Schema \u0026 documentation, 77 against 0", "Agent ergonomics, 72 against 0", "Security \u0026 auth, 46 against 0", "Transparency \u0026 trust, 66 against 41" ], "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" } ], "job": { "capability": "booking.reservations", "name": "Restaurant reservations" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chope-vs-eat-app.json", "title": "Chope vs Eat App Partner API", "url": "https://www.anchorterminal.com/compare/chope-vs-eat-app" }, { "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-resy.json", "title": "Chope vs Resy", "url": "https://www.anchorterminal.com/compare/chope-vs-resy" }, { "json": "https://www.anchorterminal.com/compare/chope-vs-sevenrooms.json", "title": "Chope vs SevenRooms", "url": "https://www.anchorterminal.com/compare/chope-vs-sevenrooms" }, { "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/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/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/chope-vs-square-appointments.json", "title": "Chope vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/chope-vs-square-appointments" }, { "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" } ], "scores": [ { "by": 65, "chope": 15, "edge": "tablecheck", "key": "reliability", "name": "Reliability", "tablecheck": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 77, "chope": 0, "edge": "tablecheck", "key": "schema", "name": "Schema \u0026 documentation", "tablecheck": 77, "weight": 13 }, { "by": 72, "chope": 0, "edge": "tablecheck", "key": "ergonomics", "name": "Agent ergonomics", "tablecheck": 72, "weight": 13 }, { "by": 46, "chope": 0, "edge": "tablecheck", "key": "security", "name": "Security \u0026 auth", "tablecheck": 46, "weight": 14 }, { "by": 30, "chope": 30, "edge": "chope", "key": "payments", "name": "Payments \u0026 pricing", "tablecheck": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 1, "chope": 34, "edge": "tablecheck", "key": "maintenance", "name": "Maintenance \u0026 community", "tablecheck": 35, "weight": 7 }, { "by": 25, "chope": 41, "edge": "tablecheck", "key": "transparency", "name": "Transparency \u0026 trust", "tablecheck": 66, "weight": 7 } ], "summary": "TableCheck API scores 57.1 (C) on agent readiness against Chope's 13.3 (F), and leads in 6 of 7 scored categories. Chope leads on payments \u0026 pricing. Both do restaurant reservations.", "verdicts": { "chope": "Chope is a diner-facing restaurant booking site and app in Singapore, Bangkok, Phuket, Jakarta and Bali, owned by Grab, with free bookings and app releases in September 2026. No public API or MCP server lets an outside agent search or book, and restaurant integrations run through partners such as TableCheck and SevenRooms by arrangement.", "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/chope-vs-tablecheck", "json": "https://www.anchorterminal.com/compare/chope-vs-tablecheck.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/chope-vs-tablecheck.md", "slim": "https://www.anchorterminal.com/compare/chope-vs-tablecheck.min.md" }, "markdown": "TableCheck API scores 57.1 (C) on agent readiness against Chope's 13.3 (F), and leads in 6 of 7 scored categories. Chope leads on payments \u0026 pricing. Both do restaurant reservations.\n\n- Chope: grade F, 13.3/100, rank #1057 of 1076. Markdown https://www.anchorterminal.com/tools/chope.md · JSON https://www.anchorterminal.com/api/v1/tools/chope.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### Chope (F)\n\nGood for: A person booking restaurants in Singapore, Thailand and Indonesia.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 0\n\nWatch for: No public API or MCP server that an outside agent can call\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 15\n- Schema \u0026 documentation, 77 against 0\n- Agent ergonomics, 72 against 0\n- Security \u0026 auth, 46 against 0\n- Transparency \u0026 trust, 66 against 41\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\n## Score by category\n\n| Category | Weight | Chope | TableCheck API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 80 | TableCheck API +65 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 0 | 77 | TableCheck API +77 |\n| Agent ergonomics | 13% (16.2 this run) | 0 | 72 | TableCheck API +72 |\n| Security \u0026 auth | 14% (17.5 this run) | 0 | 46 | TableCheck API +46 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 0 | Chope +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 34 | 35 | TableCheck API +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 41 | 66 | TableCheck API +25 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **13.3 · F** | **57.1 · C** | |\n\n## Facts side by side\n\n| Fact | Chope | TableCheck API |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | The Chope Group Pte Ltd | TableCheck Inc. |\n| Hosted endpoint | no (local only) | `https://api.tablecheck.com/api/` |\n| Transports | | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Free | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Chope's Terms \u0026 Conditions | 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| Last release | 2026-09-30 | none |\n| Terms last updated | 2023-09-11 | 2022-10-11 |\n| Privacy policy last updated | 2023-09-11 | 2016-12-14 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n\n## Verdicts\n\n**Chope.** Chope is a diner-facing restaurant booking site and app in Singapore, Bangkok, Phuket, Jakarta and Bali, owned by Grab, with free bookings and app releases in September 2026. No public API or MCP server lets an outside agent search or book, and restaurant integrations run through partners such as TableCheck and SevenRooms by arrangement.\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### Chope\n\n1. Don't plan to call Chope from another agent. Hand the booking to the person, who can use the Chope site, the app or Grab Dine Out\n2. For a restaurant on Chope that also uses TableCheck or SevenRooms, check whether that platform's API covers the venue\n3. Tell the person that some restaurants ask for a deposit, which depends on the restaurant, day and party size\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, Chope or TableCheck API?\n\nTableCheck API scores 57.1 (C) on agent readiness against Chope's 13.3 (F), and leads in 6 of 7 scored categories. Chope leads on payments \u0026 pricing.\n\n### Can an agent call Chope and TableCheck API without installing anything?\n\nNo hosted endpoint is listed for Chope. TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/chope-vs-tablecheck.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chope-vs-tablecheck.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"chope\", \"b\": \"tablecheck\"}`. From a terminal: `anchor compare chope tablecheck`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/chope.json and https://www.anchorterminal.com/api/v1/tools/tablecheck.json\n\n## Other comparisons with Chope or TableCheck API\n\n- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.md)\n- [Chope vs OpenTable APIs](https://www.anchorterminal.com/compare/chope-vs-opentable.md)\n- [Chope vs Resy](https://www.anchorterminal.com/compare/chope-vs-resy.md)\n- [Chope vs SevenRooms](https://www.anchorterminal.com/compare/chope-vs-sevenrooms.md)\n- [Chope vs TheFork B2B API](https://www.anchorterminal.com/compare/chope-vs-thefork.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- [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- [Chope vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/chope-vs-square-appointments.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", "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": "Chope vs TableCheck API", "url": "" } ], "description": "TableCheck scores 57.1 (C) to Chope's 13.3 (F) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Chope F 13.3", "TableCheck API C 57.1", "scores" ], "h1": "Chope vs TableCheck API", "image": "https://www.anchorterminal.com/assets/og/compare-chope-vs-tablecheck.png", "path": "/compare/chope-vs-tablecheck", "published": "2026-10-01", "section": "tools", "title": "Chope vs TableCheck for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/chope-vs-tablecheck" }, "tokens": { "markdown": 2050, "slim": 630 }, "version": 1 }