Head to head · Booking availability · October 2026 research run
OpenTable APIs vs 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. Both do booking availability.
Best restaurant reservation and local appointment APIs for AI agents · All 36 bookings comparisons
Which one, for what
Best 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
Best 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 this run | OpenTable APIs | Resy | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 35 | 25 | OpenTable APIs +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 61 | 0 | OpenTable APIs +61 |
| Agent ergonomics | 13%16.2 | 69 | 0 | OpenTable APIs +69 |
| Security & auth | 14%17.5 | 33 | 3 | OpenTable APIs +30 |
| Payments & pricing | 10%12.5 | 5 | 0 | OpenTable APIs +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 5 | 25 | Resy +20 |
| Transparency & trust | 7%8.8 | 42 | 30 | OpenTable APIs +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 38.6/100 | F 10.3/100 |
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
- Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes
- Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated
- Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner
- Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel
- Ask the OpenTable representative for the rate limit of each endpoint before going live
Resy
- 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
- 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.
Other comparisons with OpenTable APIs or Resy
- Chope vs OpenTable APIs
- Chope vs Resy
- Eat App Partner API vs OpenTable APIs
- Eat App Partner API vs Resy
- OpenTable APIs vs Tock
- Resy vs SevenRooms
- Resy vs TableCheck API
- Resy vs TheFork B2B API
- Resy vs Tock
- OpenTable APIs vs SevenRooms
- OpenTable APIs vs Square Appointments (Bookings API)
- OpenTable APIs vs TableCheck API
- OpenTable APIs vs TheFork B2B API
- Resy vs Square Appointments (Bookings API)
Machine-readable
- This page as Markdown
/compare/opentable-vs-resy.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/opentable.json·/api/v1/tools/resy.json - From a terminal
anchor compare opentable resy(the CLI) - Over MCP
compare_tools {"a": "opentable", "b": "resy"}at/mcp, no key