Head to head · Restaurant reservations · October 2026 research run
Chope vs TheFork B2B API
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 & pricing and maintenance & community. 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 5
- Maintenance & community, 34 against 15
Watch for
No public API or MCP server that an outside agent can call
Best for CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.
Ahead on
- Reliability, 35 against 15
- Schema & documentation, 87 against 0
- Agent ergonomics, 56 against 0
- Security & auth, 42 against 0
- Transparency & trust, 47 against 41
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants
Score by category
| Category | Weight this run | Chope | TheFork B2B API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 15 | 35 | TheFork B2B API +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 0 | 87 | TheFork B2B API +87 |
| Agent ergonomics | 13%16.2 | 0 | 56 | TheFork B2B API +56 |
| Security & auth | 14%17.5 | 0 | 42 | TheFork B2B API +42 |
| Payments & pricing | 10%12.5 | 30 | 5 | Chope +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 34 | 15 | Chope +19 |
| Transparency & trust | 7%8.8 | 41 | 47 | TheFork B2B API +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 13.3/100 | E 43.6/100 |
Facts side by side
| Fact | Chope | TheFork B2B API |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | The Chope Group Pte Ltd | TheFork (La Fourchette SAS) |
| Hosted endpoint | no (local only) | https://api.thefork.io/manager |
| Transports | HTTP | |
| Auth | OAuth or key | OAuth |
| Pricing | Free | Your plan |
| x402 | no | no |
| Licence | Proprietary service under Chope's Terms & Conditions | Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-09-30 | none |
| Terms last updated | 2023-09-11 | |
| Privacy policy last updated | 2023-09-11 | no document linked |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | yes | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | yes | |
| Arbitration or class-action waiver | 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.
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.
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
TheFork B2B API
- 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
Questions
Which is better for AI agents, Chope or TheFork B2B API?
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 & pricing and maintenance & community.
Can an agent call Chope and TheFork B2B API without installing anything?
No hosted endpoint is listed for Chope. TheFork B2B API has a hosted endpoint at https://api.thefork.io/manager.
Other comparisons with Chope or TheFork B2B API
- Chope vs Eat App Partner API
- Chope vs OpenTable APIs
- Chope vs Resy
- Chope vs SevenRooms
- Chope vs TableCheck API
- Chope vs Tock
- Eat App Partner API vs TheFork B2B API
- Resy vs TheFork B2B API
- TheFork B2B API vs Tock
- Chope vs Square Appointments (Bookings API)
- OpenTable APIs vs TheFork B2B API
- Square Appointments (Bookings API) vs TheFork B2B API
- TableCheck API vs TheFork B2B API
- SevenRooms vs TheFork B2B API
Machine-readable
- This page as Markdown
/compare/chope-vs-thefork.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/chope.json·/api/v1/tools/thefork.json - From a terminal
anchor compare chope thefork(the CLI) - Over MCP
compare_tools {"a": "chope", "b": "thefork"}at/mcp, no key