{ "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": "OpenTable APIs scores 38.6 (E) on agent readiness against Chope's 13.3 (F), and leads in 5 of 7 scored categories. Chope leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "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" } }, "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "The Chope Group Pte Ltd", "b": "OpenTable", "name": "Vendor" }, { "a": "no (local only)", "b": "https://platform.opentable.com", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Free", "b": "Your plan", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Chope's Terms \u0026 Conditions", "b": "Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation", "name": "Licence" }, { "a": "no", "b": "no", "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": "couldn't be read", "name": "Terms last updated" }, { "a": "2023-09-11", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "OpenTable APIs scores 38.6 (E) on agent readiness against Chope's 13.3 (F), and leads in 5 of 7 scored categories. Chope leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Chope or OpenTable APIs?" }, { "answer": "No hosted endpoint is listed for Chope. OpenTable APIs has a hosted endpoint at https://platform.opentable.com.", "question": "Can an agent call Chope and OpenTable APIs without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 5", "Maintenance \u0026 community, 34 against 5" ], "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, 35 against 15", "Schema \u0026 documentation, 61 against 0", "Agent ergonomics, 69 against 0", "Security \u0026 auth, 33 against 0" ], "also": [ "A hosted endpoint, with nothing to install" ], "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" } ], "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-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-tablecheck.json", "title": "Chope vs TableCheck API", "url": "https://www.anchorterminal.com/compare/chope-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/chope-vs-thefork.json", "title": "Chope vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/chope-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/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-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/opentable-vs-tock.json", "title": "OpenTable APIs vs Tock", "url": "https://www.anchorterminal.com/compare/opentable-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-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-tablecheck.json", "title": "OpenTable APIs vs TableCheck API", "url": "https://www.anchorterminal.com/compare/opentable-vs-tablecheck" }, { "json": "https://www.anchorterminal.com/compare/opentable-vs-thefork.json", "title": "OpenTable APIs vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/opentable-vs-thefork" } ], "scores": [ { "by": 20, "chope": 15, "edge": "opentable", "key": "reliability", "name": "Reliability", "opentable": 35, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 61, "chope": 0, "edge": "opentable", "key": "schema", "name": "Schema \u0026 documentation", "opentable": 61, "weight": 13 }, { "by": 69, "chope": 0, "edge": "opentable", "key": "ergonomics", "name": "Agent ergonomics", "opentable": 69, "weight": 13 }, { "by": 33, "chope": 0, "edge": "opentable", "key": "security", "name": "Security \u0026 auth", "opentable": 33, "weight": 14 }, { "by": 25, "chope": 30, "edge": "chope", "key": "payments", "name": "Payments \u0026 pricing", "opentable": 5, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 29, "chope": 34, "edge": "chope", "key": "maintenance", "name": "Maintenance \u0026 community", "opentable": 5, "weight": 7 }, { "by": 1, "chope": 41, "edge": "opentable", "key": "transparency", "name": "Transparency \u0026 trust", "opentable": 42, "weight": 7 } ], "summary": "OpenTable APIs scores 38.6 (E) on agent readiness against Chope's 13.3 (F), and leads in 5 of 7 scored categories. Chope leads on payments \u0026 pricing and maintenance \u0026 community. 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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/chope-vs-opentable", "json": "https://www.anchorterminal.com/compare/chope-vs-opentable.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/chope-vs-opentable.md", "slim": "https://www.anchorterminal.com/compare/chope-vs-opentable.min.md" }, "markdown": "OpenTable APIs scores 38.6 (E) on agent readiness against Chope's 13.3 (F), and leads in 5 of 7 scored categories. Chope leads on payments \u0026 pricing and maintenance \u0026 community. 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- 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- 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 5\n- Maintenance \u0026 community, 34 against 5\n\nWatch for: No public API or MCP server that an outside agent can call\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- Reliability, 35 against 15\n- Schema \u0026 documentation, 61 against 0\n- Agent ergonomics, 69 against 0\n- Security \u0026 auth, 33 against 0\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials\n\n\n## Score by category\n\n| Category | Weight | Chope | OpenTable APIs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 35 | OpenTable APIs +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 0 | 61 | OpenTable APIs +61 |\n| Agent ergonomics | 13% (16.2 this run) | 0 | 69 | OpenTable APIs +69 |\n| Security \u0026 auth | 14% (17.5 this run) | 0 | 33 | OpenTable APIs +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 5 | Chope +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 34 | 5 | Chope +29 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 41 | 42 | OpenTable APIs +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **13.3 · F** | **38.6 · E** | |\n\n## Facts side by side\n\n| Fact | Chope | OpenTable APIs |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | The Chope Group Pte Ltd | OpenTable |\n| Hosted endpoint | no (local only) | `https://platform.opentable.com` |\n| Transports | | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Free | Your plan |\n| x402 | no | no |\n| Licence | Proprietary service under Chope's Terms \u0026 Conditions | Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-09-30 | none |\n| Terms last updated | 2023-09-11 | couldn't be read |\n| Privacy policy last updated | 2023-09-11 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\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**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## 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### 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## Questions\n\n### Which is better for AI agents, Chope or OpenTable APIs?\n\nOpenTable APIs scores 38.6 (E) on agent readiness against Chope's 13.3 (F), and leads in 5 of 7 scored categories. Chope leads on payments \u0026 pricing and maintenance \u0026 community.\n\n### Can an agent call Chope and OpenTable APIs without installing anything?\n\nNo hosted endpoint is listed for Chope. OpenTable APIs has a hosted endpoint at https://platform.opentable.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/chope-vs-opentable.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chope-vs-opentable.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"chope\", \"b\": \"opentable\"}`. From a terminal: `anchor compare chope opentable`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/chope.json and https://www.anchorterminal.com/api/v1/tools/opentable.json\n\n## Other comparisons with Chope or OpenTable APIs\n\n- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.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 TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.md)\n- [Chope vs TheFork B2B API](https://www.anchorterminal.com/compare/chope-vs-thefork.md)\n- [Chope vs Tock](https://www.anchorterminal.com/compare/chope-vs-tock.md)\n- [Eat App Partner API vs OpenTable APIs](https://www.anchorterminal.com/compare/eat-app-vs-opentable.md)\n- [OpenTable APIs vs Tock](https://www.anchorterminal.com/compare/opentable-vs-tock.md)\n- [Chope vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/chope-vs-square-appointments.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 TableCheck API](https://www.anchorterminal.com/compare/opentable-vs-tablecheck.md)\n- [OpenTable APIs vs TheFork B2B API](https://www.anchorterminal.com/compare/opentable-vs-thefork.md)\n", "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 OpenTable APIs", "url": "" } ], "description": "OpenTable scores 38.6 (E) to Chope's 13.3 (F) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Chope F 13.3", "OpenTable APIs E 38.6", "scores" ], "h1": "Chope vs OpenTable APIs", "image": "https://www.anchorterminal.com/assets/og/compare-chope-vs-opentable.png", "path": "/compare/chope-vs-opentable", "published": "2026-10-01", "section": "tools", "title": "Chope vs OpenTable for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/chope-vs-opentable" }, "tokens": { "markdown": 2050, "slim": 680 }, "version": 1 }