# Chope vs Resy

> Chope scores 13.3 (F) to Resy's 10.3 (F) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/chope-vs-resy
- Markdown: https://www.anchorterminal.com/compare/chope-vs-resy.md (~1,800 tokens)
- Slim: https://www.anchorterminal.com/compare/chope-vs-resy.min.md (~580 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/chope-vs-resy.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-14

Chope scores 13.3 (F) on agent readiness against Resy's 10.3 (F), and leads in 3 of 7 scored categories. Resy leads on reliability. Both do restaurant reservations.

- 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
- Resy: grade F, 10.3/100, rank #1068 of 1076. Markdown https://www.anchorterminal.com/tools/resy.md · JSON https://www.anchorterminal.com/api/v1/tools/resy.json
- Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md
- All 36 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md

## Which one, for what

### Chope (F)

Good for: A person booking restaurants in Singapore, Thailand and Indonesia.

Ahead on:
- Payments & pricing, 30 against 0
- Maintenance & community, 34 against 25
- Transparency & trust, 41 against 30

Watch for: No public API or MCP server that an outside agent can call

### Resy (F)

Good for: Diners booking in person through the app.

Ahead on:
- Reliability, 25 against 15

Watch for: No public API or MCP server an outside agent can call. The Amex dining MCP endpoint takes only pre-registered OAuth clients


## Score by category

| Category | Weight | Chope | Resy | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 15 | 25 | Resy +10 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 0 | 0 | even |
| Agent ergonomics | 13% (16.2 this run) | 0 | 0 | even |
| Security & auth | 14% (17.5 this run) | 0 | 3 | Resy +3 |
| Payments & pricing | 10% (12.5 this run) | 30 | 0 | Chope +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 34 | 25 | Chope +9 |
| Transparency & trust | 7% (8.8 this run) | 41 | 30 | Chope +11 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **13.3 · F** | **10.3 · F** | |

## Facts side by side

| Fact | Chope | Resy |
| --- | --- | --- |
| Kind | Platform | Platform |
| Vendor | The Chope Group Pte Ltd | Resy (American Express) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports |  |  |
| Auth | OAuth or key | OAuth |
| Pricing | Free | Paid |
| x402 | no | no |
| Licence | Proprietary service under Chope's Terms & Conditions | Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-09-30 | none |
| Terms last updated | 2023-09-11 | no document linked |
| Privacy policy last updated | 2023-09-11 | couldn't be read |
| 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.

**Resy.** Resy is a large diner reservation network, now including Tock's venues, with American Express behind it. There is no public API or MCP server an outside agent can call today. An Amex-hosted MCP endpoint exists but accepts only pre-registered clients and has no public documentation, and Resy's own terms and privacy pages could not be read.

## Before you call either

### Chope

1. 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
2. For a restaurant on Chope that also uses TableCheck or SevenRooms, check whether that platform's API covers the venue
3. Tell the person that some restaurants ask for a deposit, which depends on the restaurant, day and party size

### Resy

1. Don't plan to call Resy from another agent. Hand the booking to the person in the Resy app, or use a client that American Express has approved for its dining MCP
2. Do not automate the Resy website or app, since Resy runs a bot-detection programme against automated booking

## Questions

### Which is better for AI agents, Chope or Resy?

Chope scores 13.3 (F) on agent readiness against Resy's 10.3 (F), and leads in 3 of 7 scored categories. Resy leads on reliability.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/chope-vs-resy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chope-vs-resy.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "chope", "b": "resy"}`. From a terminal: `anchor compare chope resy`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/chope.json and https://www.anchorterminal.com/api/v1/tools/resy.json

## Other comparisons with Chope or Resy

- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.md)
- [Chope vs OpenTable APIs](https://www.anchorterminal.com/compare/chope-vs-opentable.md)
- [Chope vs SevenRooms](https://www.anchorterminal.com/compare/chope-vs-sevenrooms.md)
- [Chope vs TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.md)
- [Chope vs TheFork B2B API](https://www.anchorterminal.com/compare/chope-vs-thefork.md)
- [Chope vs Tock](https://www.anchorterminal.com/compare/chope-vs-tock.md)
- [Eat App Partner API vs Resy](https://www.anchorterminal.com/compare/eat-app-vs-resy.md)
- [Resy vs SevenRooms](https://www.anchorterminal.com/compare/resy-vs-sevenrooms.md)
- [Resy vs TableCheck API](https://www.anchorterminal.com/compare/resy-vs-tablecheck.md)
- [Resy vs TheFork B2B API](https://www.anchorterminal.com/compare/resy-vs-thefork.md)
- [Resy vs Tock](https://www.anchorterminal.com/compare/resy-vs-tock.md)
- [Chope vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/chope-vs-square-appointments.md)
- [OpenTable APIs vs Resy](https://www.anchorterminal.com/compare/opentable-vs-resy.md)
- [Resy vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/resy-vs-square-appointments.md)