# OpenTable APIs vs Resy

> OpenTable scores 38.6 (E) to Resy's 10.3 (F) for booking availability. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/opentable-vs-resy
- Markdown: https://www.anchorterminal.com/compare/opentable-vs-resy.md (~2,000 tokens)
- Slim: https://www.anchorterminal.com/compare/opentable-vs-resy.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/opentable-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

OpenTable APIs scores 38.6 (E) on agent readiness against Resy's 10.3 (F), and leads in 6 of 7 scored categories. Resy leads on maintenance & community. Both do booking availability.

- OpenTable APIs: grade E, 38.6/100, rank #994 of 1076. Markdown https://www.anchorterminal.com/tools/opentable.md · JSON https://www.anchorterminal.com/api/v1/tools/opentable.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

### OpenTable APIs (E)

Good for: Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.

Ahead on:
- Reliability, 35 against 25
- Schema & documentation, 61 against 0
- Agent ergonomics, 69 against 0
- Security & auth, 33 against 3
- Payments & pricing, 5 against 0
- Transparency & trust, 42 against 30

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials

### Resy (F)

Good for: Diners booking in person through the app.

Ahead on:
- Maintenance & community, 25 against 5

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 | OpenTable APIs | Resy | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 35 | 25 | OpenTable APIs +10 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 61 | 0 | OpenTable APIs +61 |
| Agent ergonomics | 13% (16.2 this run) | 69 | 0 | OpenTable APIs +69 |
| Security & auth | 14% (17.5 this run) | 33 | 3 | OpenTable APIs +30 |
| Payments & pricing | 10% (12.5 this run) | 5 | 0 | OpenTable APIs +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 5 | 25 | Resy +20 |
| Transparency & trust | 7% (8.8 this run) | 42 | 30 | OpenTable APIs +12 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **38.6 · E** | **10.3 · F** | |

## Facts side by side

| Fact | OpenTable APIs | Resy |
| --- | --- | --- |
| Kind | HTTP API | Platform |
| Vendor | OpenTable | Resy (American Express) |
| Hosted endpoint | `https://platform.opentable.com` | no (local only) |
| Transports | HTTP |  |
| Auth | OAuth | OAuth |
| Pricing | Your plan | Paid |
| x402 | no | no |
| Licence | Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation | 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 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | couldn't be read | couldn't be read |
| Customer content may train models | couldn't be read |  |
| Terms restrict automated access | couldn't be read |  |
| Terms restrict benchmarking | couldn't be read |  |
| Terms or service can change without notice | couldn't be read |  |
| Arbitration or class-action waiver | couldn't be read |  |

## Verdicts

**OpenTable APIs.** The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.

**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

### OpenTable APIs

1. Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes
2. Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated
3. Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner
4. Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel
5. Ask the OpenTable representative for the rate limit of each endpoint before going live

### 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, OpenTable APIs or Resy?

OpenTable APIs scores 38.6 (E) on agent readiness against Resy's 10.3 (F), and leads in 6 of 7 scored categories. Resy leads on maintenance & community.

### Can an agent call OpenTable APIs and Resy without installing anything?

OpenTable APIs has a hosted endpoint at https://platform.opentable.com. No hosted endpoint is listed for Resy.


## For agents

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

## Other comparisons with OpenTable APIs or Resy

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