Head to head · Restaurant reservations · October 2026 research run
Chope vs TableCheck API
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 & pricing. Both do restaurant reservations.
Best restaurant reservation and local appointment APIs for AI agents · All 36 bookings comparisons
Which one, for what
Chope F
Best for A person booking restaurants in Singapore, Thailand and Indonesia.
Ahead on
- Payments & pricing, 30 against 0
Watch for
No public API or MCP server that an outside agent can call
Best for Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.
Ahead on
- Reliability, 80 against 15
- Schema & documentation, 77 against 0
- Agent ergonomics, 72 against 0
- Security & auth, 46 against 0
- Transparency & trust, 66 against 41
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
Access needs an emailed application, case-by-case approval and fees quoted privately
Score by category
| Category | Weight this run | Chope | TableCheck API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 15 | 80 | TableCheck API +65 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 0 | 77 | TableCheck API +77 |
| Agent ergonomics | 13%16.2 | 0 | 72 | TableCheck API +72 |
| Security & auth | 14%17.5 | 0 | 46 | TableCheck API +46 |
| Payments & pricing | 10%12.5 | 30 | 0 | Chope +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 34 | 35 | TableCheck API +1 |
| Transparency & trust | 7%8.8 | 41 | 66 | TableCheck API +25 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 13.3/100 | C 57.1/100 |
Facts side by side
| Fact | Chope | TableCheck API |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | The Chope Group Pte Ltd | TableCheck Inc. |
| Hosted endpoint | no (local only) | https://api.tablecheck.com/api/ |
| Transports | HTTP, Streamable HTTP | |
| Auth | OAuth or key | API key |
| Pricing | Free | Paid |
| x402 | no | no |
| Licence | Proprietary service under Chope's Terms & Conditions | Proprietary service under the TableCheck API Terms of Service |
| Tools exposed | none | 20 |
| Read-only variant documented | no | yes |
| llms.txt | no | no |
| Last release | 2026-09-30 | none |
| Terms last updated | 2023-09-11 | 2022-10-11 |
| Privacy policy last updated | 2023-09-11 | 2016-12-14 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
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 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.
Before you call either
Chope
- 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
TableCheck API
- 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
Questions
Which is better for AI agents, Chope or TableCheck API?
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 & pricing.
Can an agent call Chope and TableCheck API without installing anything?
No hosted endpoint is listed for Chope. TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/.
Other comparisons with Chope or TableCheck API
- Chope vs Eat App Partner API
- Chope vs OpenTable APIs
- Chope vs Resy
- Chope vs SevenRooms
- Chope vs TheFork B2B API
- Chope vs Tock
- Eat App Partner API vs TableCheck API
- Resy vs TableCheck API
- TableCheck API vs Tock
- Chope vs Square Appointments (Bookings API)
- OpenTable APIs vs TableCheck API
- Square Appointments (Bookings API) vs TableCheck API
- TableCheck API vs TheFork B2B API
- SevenRooms vs TableCheck API
Machine-readable
- This page as Markdown
/compare/chope-vs-tablecheck.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/chope.json·/api/v1/tools/tablecheck.json - From a terminal
anchor compare chope tablecheck(the CLI) - Over MCP
compare_tools {"a": "chope", "b": "tablecheck"}at/mcp, no key