Head to head · Restaurant reservations · October 2026 research run
OpenTable APIs vs Tock
OpenTable APIs scores 38.6 (E) on agent readiness against Tock's 12.4 (F), and leads in 5 of 7 scored categories. Tock leads on maintenance & community and transparency & trust. Both do restaurant reservations.
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 5
- Agent ergonomics, 69 against 0
- Security & auth, 33 against 0
- Payments & pricing, 5 against 0
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
Tock F
Best for Restaurants and wineries taking reservations and experience bookings, and for diners booking in person.
Ahead on
- Maintenance & community, 23 against 5
- Transparency & trust, 52 against 42
Watch for
No public API or MCP server an outside agent can call. The docs index reads "Docs coming soon"
Score by category
| Category | Weight this run | OpenTable APIs | Tock | 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 | 5 | OpenTable APIs +56 |
| Agent ergonomics | 13%16.2 | 69 | 0 | OpenTable APIs +69 |
| Security & auth | 14%17.5 | 33 | 0 | OpenTable APIs +33 |
| 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 | 23 | Tock +18 |
| Transparency & trust | 7%8.8 | 42 | 52 | Tock +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 38.6/100 | F 12.4/100 |
Facts side by side
| Fact | OpenTable APIs | Tock |
|---|---|---|
| Kind | HTTP API | Platform |
| Vendor | OpenTable | Tock (American Express) |
| Hosted endpoint | https://platform.opentable.com | no (local only) |
| Transports | HTTP | |
| Auth | OAuth | API key |
| 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 under the Tock Terms of Use (effective 12 February 2026) and merchant terms |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Terms last updated | couldn't be read | 2026-02-12 |
| Privacy policy last updated | couldn't be read | 2025-11-24 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |
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.
Tock
Tock takes reservations and experience bookings for restaurants and wineries and now feeds its venues into Resy. There is no public API or MCP server an outside agent can call today. api.exploretock.com publishes reservation data models without endpoints, and the Terms of Use forbid automated access to the site.
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
Tock
- Don't plan to call Tock from another agent. Hand the booking to the person on exploretock.com or in the Resy app
- Do not script the Tock website, which the Terms of Use forbid. A venue wanting data should ask Tock through its dashboard account
Questions
Which is better for AI agents, OpenTable APIs or Tock?
OpenTable APIs scores 38.6 (E) on agent readiness against Tock's 12.4 (F), and leads in 5 of 7 scored categories. Tock leads on maintenance & community and transparency & trust.
Can an agent call OpenTable APIs and Tock without installing anything?
OpenTable APIs has a hosted endpoint at https://platform.opentable.com. No hosted endpoint is listed for Tock.
Other comparisons with OpenTable APIs or Tock
- Chope vs OpenTable APIs
- Chope vs Tock
- Eat App Partner API vs OpenTable APIs
- Eat App Partner API vs Tock
- Resy vs Tock
- TableCheck API vs Tock
- TheFork B2B API vs Tock
- OpenTable APIs vs Resy
- OpenTable APIs vs SevenRooms
- OpenTable APIs vs Square Appointments (Bookings API)
- OpenTable APIs vs TableCheck API
- OpenTable APIs vs TheFork B2B API
- SevenRooms vs Tock
- Square Appointments (Bookings API) vs Tock
Machine-readable
- This page as Markdown
/compare/opentable-vs-tock.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/opentable.json·/api/v1/tools/tock.json - From a terminal
anchor compare opentable tock(the CLI) - Over MCP
compare_tools {"a": "opentable", "b": "tock"}at/mcp, no key