{ "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": "Eat App Partner API scores 53.4 (D) 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": "eat-app", "name": "Eat App Partner API", "vendor": "Eat App (EAT APPLICATION DMCC)", "vendorUrl": "https://restaurant.eatapp.co", "kind": "http-api", "category": "local-bookings", "summary": "Eat App is a restaurant reservation and table management system. Its Partner API lets booking channels check availability and create, change and cancel reservations, a Concierge API serves restaurant groups, and a read-only Restaurant MCP server connects AI assistants.", "url": "https://www.anchorterminal.com/tools/eat-app", "markdownUrl": "https://www.anchorterminal.com/tools/eat-app.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/eat-app.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/eat-app.json", "license": "Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements", "transports": [ "http" ], "remoteUrl": "https://api.eatapp.co/partners/v2", "packages": [], "auth": "mixed", "authNotes": "Partner approval required for the Partner API. A booking channel asks to become a partner (info@eatapp.co), Eat App activates partnerships restaurant by restaurant, and its support team issues a long-term API key sent as a Bearer token. A login endpoint also exchanges the partner's email and password for a 24-hour token. Concierge API keys are created by Eat App for restaurant groups. The Restaurant MCP server uses OAuth with dynamic client registration, PKCE and a single `mcp` scope, and the restaurant signs in with its Eat App login.", "pricing": "paid", "pricingNotes": "No per-call price. The pricing page marks API access in the Enterprise column only (Let's talk) and lists API and webhooks access as an add-on. Table management plans are $99, $199 and $389 a month, or $69, $159 and $299 billed yearly, with a 14-day trial and a $0 plan limited to 100 guests a month. The Restaurant MCP needs an active table management subscription. A sandbox host (api.eat-sandbox.co) is given to partners (https://restaurant.eatapp.co/pricing).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Partner or Concierge API docs, the MCP guide or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://documenter.getpostman.com/view/6173104/S1Lr4Av4", "capabilities": [ "booking.reservations", "booking.availability", "booking.venue", "crm.records", "events.webhooks-send" ], "tags": [ "hosted", "closed-source", "partner-only", "rest", "mcp", "oauth", "sandbox", "status-page", "webhooks", "restaurants" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 53.4, "grade": "D", "agentReady": false, "rank": 752, "ranked": true, "rankOf": 1076, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 40, "payments": 15, "reliability": 78, "schema": 59, "security": 43, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.", "bestFor": "Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.", "strengths": [ "idempotency_token on Create Reservation returns the first success for a repeated request", "60 requests a minute stated, with a documented 429 body", "Better Stack status page with separate Partner API and Concierge API components and incident history", "Dated API changelog, latest entry 13 October 2026", "Restaurant MCP server with OAuth dynamic client registration and read-only access" ], "weaknesses": [ "A booking channel can book only at restaurants whose partnership Eat App has activated", "API access sits in the Enterprise column of the pricing page, priced through sales", "No OpenAPI file, llms.txt or SDK, only Postman collections", "A login endpoint accepts the partner's email and password for a 24-hour token", "No security.txt, and the trust centre content did not load for our reader" ], "agentNotes": [ "Send a unique idempotency_token with each new booking so a retry returns the first result", "Use POST /partners/v2/availability/range, not the legacy availability endpoint", "Keep include_tables ranges to 24 hours or less and pass covers with it", "Stay under 60 requests a minute and wait for the next minute after a 429", "Cancel by PATCH with status canceled, after which the reservation can no longer change" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.4 } ], "editorialScores": { "ergonomics": 66, "maintenance": 40, "payments": 15, "reliability": 78, "schema": 59, "security": 43, "transparency": 32 }, "provenanceScore": 71 }, "connect": { "http": "curl 'https://api.eat-sandbox.co/partners/v2/reservations' -H 'Authorization: Bearer API_TOKEN' -H 'Content-Type: application/json' -H 'Accept-Encoding: gzip'" }, "letme": { "capability": "https://letme.dev/booking.reservations", "tool": "https://letme.dev/eat-app" }, "area": "everyday", "provenance": { "legalEntity": "EAT APPLICATION DMCC", "domain": "eatapp.co", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://restaurant.eatapp.co/terms", "privacy": "https://restaurant.eatapp.co/privacy", "statusPage": "https://status.eatapp.co", "changelog": "https://documenter.getpostman.com/view/6173104/S1Lr4Av4", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The terms of service (effective 10 September 2025) are entered into by EAT APPLICATION DMCC, Jumeirah Lake Towers, Dubai, licence DMCC-164040, and say the agreement also includes one executed with its licensee Swiggy Limited.", "The privacy policy names EAT APPLICATION DMCC and covers GDPR rights and a retention statement without fixed periods.", "The API changelog is a section of the Partner API Postman documentation.", "security.txt returns 404 on eatapp.co, restaurant.eatapp.co and api.eatapp.co. A trust centre at trust.eatapp.co loads by script and showed only its title to our reader.", "RDAP for eatapp.co did not answer, so the registration date is not recorded." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/eat-app.json", "live": { "slug": "eat-app", "probe": { "target": "https://api.eatapp.co/partners/v2", "method": "get", "lastAt": "2026-10-14T09:41:49.444870422Z", "lastOk": true, "lastStatus": 404, "lastMs": 157, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 175, "p95ms24h": 322, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.eatapp.co", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:05.16851429Z" }, "updatedAt": "2026-10-14T09:41:49.444870422Z" } }, "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "The Chope Group Pte Ltd", "b": "Eat App (EAT APPLICATION DMCC)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.eatapp.co/partners/v2", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or 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 Eat App's terms of service (effective 10 September 2025) and partner agreements", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-10-13", "name": "Last release" }, { "a": "2023-09-11", "b": "2025-09-10", "name": "Terms last updated" }, { "a": "2023-09-11", "b": "no date given", "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": "Eat App Partner API scores 53.4 (D) 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 Eat App Partner API?" }, { "answer": "No hosted endpoint is listed for Chope. Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2.", "question": "Can an agent call Chope and Eat App Partner API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 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, 78 against 15", "Schema \u0026 documentation, 59 against 0", "Agent ergonomics, 66 against 0", "Security \u0026 auth, 43 against 0", "Maintenance \u0026 community, 40 against 34", "Transparency \u0026 trust, 52 against 41" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.", "slug": "eat-app", "watchFor": "A booking channel can book only at restaurants whose partnership Eat App has activated" } ], "job": { "capability": "booking.reservations", "name": "Restaurant reservations" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chope-vs-opentable.json", "title": "Chope vs OpenTable APIs", "url": "https://www.anchorterminal.com/compare/chope-vs-opentable" }, { "json": "https://www.anchorterminal.com/compare/chope-vs-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/eat-app-vs-resy.json", "title": "Eat App Partner API vs Resy", "url": "https://www.anchorterminal.com/compare/eat-app-vs-resy" }, { "json": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.json", "title": "Eat App Partner API vs SevenRooms", "url": "https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms" }, { "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-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/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/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/eat-app-vs-square-appointments.json", "title": "Eat App Partner API vs Square Appointments (Bookings API)", "url": "https://www.anchorterminal.com/compare/eat-app-vs-square-appointments" } ], "scores": [ { "by": 63, "chope": 15, "eat-app": 78, "edge": "eat-app", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 59, "chope": 0, "eat-app": 59, "edge": "eat-app", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 66, "chope": 0, "eat-app": 66, "edge": "eat-app", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 43, "chope": 0, "eat-app": 43, "edge": "eat-app", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 15, "chope": 30, "eat-app": 15, "edge": "chope", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "chope": 34, "eat-app": 40, "edge": "eat-app", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 11, "chope": 41, "eat-app": 52, "edge": "eat-app", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Eat App Partner API scores 53.4 (D) 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.", "eat-app": "A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/chope-vs-eat-app", "json": "https://www.anchorterminal.com/compare/chope-vs-eat-app.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/chope-vs-eat-app.md", "slim": "https://www.anchorterminal.com/compare/chope-vs-eat-app.min.md" }, "markdown": "Eat App Partner API scores 53.4 (D) 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- Eat App Partner API: grade D, 53.4/100, rank #752 of 1076. Markdown https://www.anchorterminal.com/tools/eat-app.md · JSON https://www.anchorterminal.com/api/v1/tools/eat-app.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 15\n\nWatch for: No public API or MCP server that an outside agent can call\n\n### Eat App Partner API (D)\n\nGood for: Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.\n\nAhead on:\n- Reliability, 78 against 15\n- Schema \u0026 documentation, 59 against 0\n- Agent ergonomics, 66 against 0\n- Security \u0026 auth, 43 against 0\n- Maintenance \u0026 community, 40 against 34\n- Transparency \u0026 trust, 52 against 41\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: A booking channel can book only at restaurants whose partnership Eat App has activated\n\n\n## Score by category\n\n| Category | Weight | Chope | Eat App Partner API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 78 | Eat App Partner API +63 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 0 | 59 | Eat App Partner API +59 |\n| Agent ergonomics | 13% (16.2 this run) | 0 | 66 | Eat App Partner API +66 |\n| Security \u0026 auth | 14% (17.5 this run) | 0 | 43 | Eat App Partner API +43 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 15 | Chope +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 34 | 40 | Eat App Partner API +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 41 | 52 | Eat App Partner API +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **13.3 · F** | **53.4 · D** | |\n\n## Facts side by side\n\n| Fact | Chope | Eat App Partner API |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | The Chope Group Pte Ltd | Eat App (EAT APPLICATION DMCC) |\n| Hosted endpoint | no (local only) | `https://api.eatapp.co/partners/v2` |\n| Transports | | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Free | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Chope's Terms \u0026 Conditions | Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements |\n| Read-only variant documented | no | yes |\n| llms.txt | no | no |\n| Last release | 2026-09-30 | 2026-10-13 |\n| Terms last updated | 2023-09-11 | 2025-09-10 |\n| Privacy policy last updated | 2023-09-11 | no date given |\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**Eat App Partner API.** A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.\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### Eat App Partner API\n\n1. Send a unique idempotency_token with each new booking so a retry returns the first result\n2. Use POST /partners/v2/availability/range, not the legacy availability endpoint\n3. Keep include_tables ranges to 24 hours or less and pass covers with it\n4. Stay under 60 requests a minute and wait for the next minute after a 429\n5. Cancel by PATCH with status canceled, after which the reservation can no longer change\n\n## Questions\n\n### Which is better for AI agents, Chope or Eat App Partner API?\n\nEat App Partner API scores 53.4 (D) 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 Eat App Partner API without installing anything?\n\nNo hosted endpoint is listed for Chope. Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/chope-vs-eat-app.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chope-vs-eat-app.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"chope\", \"b\": \"eat-app\"}`. From a terminal: `anchor compare chope eat-app`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/chope.json and https://www.anchorterminal.com/api/v1/tools/eat-app.json\n\n## Other comparisons with Chope or Eat App Partner API\n\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 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- [Eat App Partner API vs Resy](https://www.anchorterminal.com/compare/eat-app-vs-resy.md)\n- [Eat App Partner API vs SevenRooms](https://www.anchorterminal.com/compare/eat-app-vs-sevenrooms.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 TheFork B2B API](https://www.anchorterminal.com/compare/eat-app-vs-thefork.md)\n- [Eat App Partner API vs Tock](https://www.anchorterminal.com/compare/eat-app-vs-tock.md)\n- [Chope vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/chope-vs-square-appointments.md)\n- [Eat App Partner API vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.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 Eat App Partner API", "url": "" } ], "description": "Eat App Partner scores 53.4 (D) to Chope's 13.3 (F) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Chope F 13.3", "Eat App Partner API D 53.4", "scores" ], "h1": "Chope vs Eat App Partner API", "image": "https://www.anchorterminal.com/assets/og/compare-chope-vs-eat-app.png", "path": "/compare/chope-vs-eat-app", "published": "2026-10-01", "section": "tools", "title": "Chope vs Eat App Partner for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/chope-vs-eat-app" }, "tokens": { "markdown": 2050, "slim": 680 }, "version": 1 }