{ "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": "TheFork B2B API scores 43.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": "thefork", "name": "TheFork B2B API", "vendor": "TheFork (La Fourchette SAS)", "vendorUrl": "https://www.thefork.com", "kind": "http-api", "category": "local-bookings", "summary": "TheFork's B2B API lets restaurants and their software partners, such as CRM vendors and AI phone agents, read availability and create, change and cancel reservations in TheFork Manager, with webhooks, reviews and customer data.", "url": "https://www.anchorterminal.com/tools/thefork", "markdownUrl": "https://www.anchorterminal.com/tools/thefork.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/thefork.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/thefork.json", "license": "Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork", "transports": [ "http" ], "remoteUrl": "https://api.thefork.io/manager", "packages": [], "auth": "oauth", "authNotes": "Partner approval required. Credentials are requested from the integrations team at integrations@thefork.com with a company name and use case. TheFork sends a client_id and client_secret through a secure channel, and the client exchanges them at https://auth.thefork.io/oauth/token (OAuth 2.0 client credentials, audience https://api.thefork.io) for a Bearer token that lasts 8,600 seconds. Nine scopes limit each client, from full access (tfm-restaurant) to read-only availability. restaurantUuid and groupUuid values for each restaurant come from TheFork, as no endpoint lists them.", "pricing": "byo-plan", "pricingNotes": "No API prices are published. Access follows a partnership with TheFork, and the rate limit is set by contract. The API terms mention test data for pre-launch testing. No sandbox host or self-serve tier is documented (https://docs.thefork.io/getting-started).", "priceSummary": "Your plan", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer portal, llms.txt or OpenAPI schema (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.thefork.io/B2B-API/introduction", "llmsTxt": "https://docs.thefork.io/B2B-API/llms.txt", "openapi": "https://api.thefork.io/manager/openapi.json", "capabilities": [ "booking.reservations", "booking.availability", "booking.venue", "crm.records", "events.webhooks-send" ], "tags": [ "hosted", "closed-source", "partner-only", "rest", "oauth", "openapi", "llms-txt", "webhooks", "eu", "restaurants" ], "graded": true, "anchor": { "graded": true, "score": 43.6, "grade": "E", "agentReady": false, "rank": 951, "ranked": true, "rankOf": 1076, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 15, "payments": 5, "reliability": 35, "schema": 87, "security": 42, "transparency": 47 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices.", "bestFor": "CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.", "strengths": [ "OpenAPI 3.1 schema generated from the deployed code, with 19 operations, enums, examples and error responses", "llms.txt for the B2B API covers scopes per endpoint, time zones, reservation statuses and error formats", "Nine OAuth scopes, including read-only availability and a separate scope for unrestricted bookings that is off by default", "Business error codes such as NO_AVAILABILITY, DOUBLE_BOOKING and RESERVATION_NOT_FOUND", "Written versioning policy with 6 months of support for the previous version" ], "weaknesses": [ "Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants", "Credentials come from the integrations team by email after approval, with no self-serve route", "Timeslots that need a payment guarantee cannot be booked through the API", "The status page at status.thefork.io redirects to a private Rootly page that needs a sign-in", "No changelog, idempotency key or published production rate limit" ], "agentNotes": [ "Read hasPaymentGuaranteeRequirement in the timeslots response before booking, since the API cannot take a card", "Check the status field after creating a reservation and treat REQUESTED as unconfirmed", "Send the timeslot datetime unchanged as mealDate, because times are the restaurant's local time", "Check for an existing reservation before retrying a failed POST, as no idempotency key exists and 409 signals DOUBLE_BOOKING", "Cache the access token for its 8,600 seconds and do not request a new one while it is valid" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.6 } ], "editorialScores": { "ergonomics": 56, "maintenance": 15, "payments": 5, "reliability": 35, "schema": 87, "security": 42, "transparency": 33 }, "provenanceScore": 60 }, "connect": { "http": "curl -X POST https://auth.thefork.io/oauth/token -H 'Content-Type: application/x-www-form-urlencoded' -d 'audience=https://api.thefork.io\u0026grant_type=client_credentials\u0026client_id=CLIENT_ID\u0026client_secret=CLIENT_SECRET'" }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/thefork" }, "area": "everyday", "provenance": { "legalEntity": "La Fourchette SAS", "domain": "thefork.io", "domainRegistered": "2016-05-30", "endpointOnVendorDomain": true, "terms": "https://docs.thefork.io/pdf/LaFourchette-Partners-API-Licence-2.pdf", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The developer portal footer links the TheFork Partners API Terms of Use, a PDF naming La Fourchette SAS, 70 rue Saint Lazare, Paris, company number 494 447 949, where no core agreement exists.", "www.thefork.com answered with a bot check (403), so its privacy policy and terms were not read and no privacy URL is recorded.", "status.thefork.io redirects to a private Rootly status page that needs a sign-in, so no public status page is recorded.", "www.thefork.com/.well-known/security.txt returns 404 and docs.thefork.io/.well-known/security.txt returns 403.", "No changelog was found. docs.thefork.io/changelog returns 403.", "RDAP gives thefork.io a registration date of 2016-05-30 and thefork.com 1998-11-04." ], "score": 60 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/thefork.json", "live": { "slug": "thefork", "probe": { "target": "https://api.thefork.io/manager", "method": "get", "lastAt": "2026-10-14T09:42:10.255461561Z", "lastOk": true, "lastStatus": 404, "lastMs": 57, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 56, "p95ms24h": 119, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "updatedAt": "2026-10-14T09:42:10.255461561Z" } }, "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "The Chope Group Pte Ltd", "b": "TheFork (La Fourchette SAS)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.thefork.io/manager", "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 TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "none", "name": "Last release" }, { "a": "2023-09-11", "b": "", "name": "Terms last updated" }, { "a": "2023-09-11", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "yes", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "TheFork B2B API scores 43.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 TheFork B2B API?" }, { "answer": "No hosted endpoint is listed for Chope. TheFork B2B API has a hosted endpoint at https://api.thefork.io/manager.", "question": "Can an agent call Chope and TheFork B2B API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 5", "Maintenance \u0026 community, 34 against 15" ], "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, 87 against 0", "Agent ergonomics, 56 against 0", "Security \u0026 auth, 42 against 0", "Transparency \u0026 trust, 47 against 41" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.", "slug": "thefork", "watchFor": "Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants" } ], "job": { "capability": "booking.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-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-thefork.json", "title": "Eat App Partner API vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/eat-app-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/resy-vs-thefork.json", "title": "Resy vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/resy-vs-thefork" }, { "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/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-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-thefork.json", "title": "Square Appointments (Bookings API) vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/square-appointments-vs-thefork" }, { "json": "https://www.anchorterminal.com/compare/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-thefork.json", "title": "SevenRooms vs TheFork B2B API", "url": "https://www.anchorterminal.com/compare/sevenrooms-vs-thefork" } ], "scores": [ { "by": 20, "chope": 15, "edge": "thefork", "key": "reliability", "name": "Reliability", "thefork": 35, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 87, "chope": 0, "edge": "thefork", "key": "schema", "name": "Schema \u0026 documentation", "thefork": 87, "weight": 13 }, { "by": 56, "chope": 0, "edge": "thefork", "key": "ergonomics", "name": "Agent ergonomics", "thefork": 56, "weight": 13 }, { "by": 42, "chope": 0, "edge": "thefork", "key": "security", "name": "Security \u0026 auth", "thefork": 42, "weight": 14 }, { "by": 25, "chope": 30, "edge": "chope", "key": "payments", "name": "Payments \u0026 pricing", "thefork": 5, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 19, "chope": 34, "edge": "chope", "key": "maintenance", "name": "Maintenance \u0026 community", "thefork": 15, "weight": 7 }, { "by": 6, "chope": 41, "edge": "thefork", "key": "transparency", "name": "Transparency \u0026 trust", "thefork": 47, "weight": 7 } ], "summary": "TheFork B2B API scores 43.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.", "thefork": "A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/chope-vs-thefork", "json": "https://www.anchorterminal.com/compare/chope-vs-thefork.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/chope-vs-thefork.md", "slim": "https://www.anchorterminal.com/compare/chope-vs-thefork.min.md" }, "markdown": "TheFork B2B API scores 43.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- TheFork B2B API: grade E, 43.6/100, rank #951 of 1076. Markdown https://www.anchorterminal.com/tools/thefork.md · JSON https://www.anchorterminal.com/api/v1/tools/thefork.json\n- Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md\n- All 36 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md\n\n## Which one, for what\n\n### 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 15\n\nWatch for: No public API or MCP server that an outside agent can call\n\n### TheFork B2B API (E)\n\nGood for: CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.\n\nAhead on:\n- Reliability, 35 against 15\n- Schema \u0026 documentation, 87 against 0\n- Agent ergonomics, 56 against 0\n- Security \u0026 auth, 42 against 0\n- Transparency \u0026 trust, 47 against 41\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants\n\n\n## Score by category\n\n| Category | Weight | Chope | TheFork B2B API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 35 | TheFork B2B API +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 0 | 87 | TheFork B2B API +87 |\n| Agent ergonomics | 13% (16.2 this run) | 0 | 56 | TheFork B2B API +56 |\n| Security \u0026 auth | 14% (17.5 this run) | 0 | 42 | TheFork B2B API +42 |\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 | 15 | Chope +19 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 41 | 47 | TheFork B2B API +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **13.3 · F** | **43.6 · E** | |\n\n## Facts side by side\n\n| Fact | Chope | TheFork B2B API |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | The Chope Group Pte Ltd | TheFork (La Fourchette SAS) |\n| Hosted endpoint | no (local only) | `https://api.thefork.io/manager` |\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 TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2026-09-30 | none |\n| Terms last updated | 2023-09-11 | |\n| Privacy policy last updated | 2023-09-11 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | yes | |\n| Terms restrict benchmarking | not found in the text | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | 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**TheFork B2B API.** A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices.\n\n## Before you call either\n\n### 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### TheFork B2B API\n\n1. Read hasPaymentGuaranteeRequirement in the timeslots response before booking, since the API cannot take a card\n2. Check the status field after creating a reservation and treat REQUESTED as unconfirmed\n3. Send the timeslot datetime unchanged as mealDate, because times are the restaurant's local time\n4. Check for an existing reservation before retrying a failed POST, as no idempotency key exists and 409 signals DOUBLE_BOOKING\n5. Cache the access token for its 8,600 seconds and do not request a new one while it is valid\n\n## Questions\n\n### Which is better for AI agents, Chope or TheFork B2B API?\n\nTheFork B2B API scores 43.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 TheFork B2B API without installing anything?\n\nNo hosted endpoint is listed for Chope. TheFork B2B API has a hosted endpoint at https://api.thefork.io/manager.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/chope-vs-thefork.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chope-vs-thefork.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"chope\", \"b\": \"thefork\"}`. From a terminal: `anchor compare chope thefork`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/chope.json and https://www.anchorterminal.com/api/v1/tools/thefork.json\n\n## Other comparisons with Chope or TheFork B2B 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 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 TheFork B2B API](https://www.anchorterminal.com/compare/eat-app-vs-thefork.md)\n- [Resy vs TheFork B2B API](https://www.anchorterminal.com/compare/resy-vs-thefork.md)\n- [TheFork B2B API vs Tock](https://www.anchorterminal.com/compare/thefork-vs-tock.md)\n- [Chope vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/chope-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 TheFork B2B API](https://www.anchorterminal.com/compare/square-appointments-vs-thefork.md)\n- [TableCheck API vs TheFork B2B API](https://www.anchorterminal.com/compare/tablecheck-vs-thefork.md)\n- [SevenRooms vs TheFork B2B API](https://www.anchorterminal.com/compare/sevenrooms-vs-thefork.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Chope vs TheFork B2B API", "url": "" } ], "description": "TheFork B2B scores 43.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", "TheFork B2B API E 43.6", "scores" ], "h1": "Chope vs TheFork B2B API", "image": "https://www.anchorterminal.com/assets/og/compare-chope-vs-thefork.png", "path": "/compare/chope-vs-thefork", "published": "2026-10-01", "section": "tools", "title": "Chope vs TheFork B2B for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/chope-vs-thefork" }, "tokens": { "markdown": 2050, "slim": 680 }, "version": 1 }