Head to head · Restaurant reservations · October 2026 research run
Eat App Partner API vs Tock
Eat App Partner API scores 53.4 (D) on agent readiness against Tock's 12.4 (F), and leads in 6 of 7 scored categories. Both do restaurant reservations.
Best restaurant reservation and local appointment APIs for AI agents · All 36 bookings comparisons
Which one, for what
Best for Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.
Ahead on
- Reliability, 78 against 25
- Schema & documentation, 59 against 5
- Agent ergonomics, 66 against 0
- Security & auth, 43 against 0
- Payments & pricing, 15 against 0
- Maintenance & community, 40 against 23
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
A booking channel can book only at restaurants whose partnership Eat App has activated
Tock F
Best for Restaurants and wineries taking reservations and experience bookings, and for diners booking in person.
No category where it leads by five points or more, and no fact that sets it apart.
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 | Eat App Partner API | Tock | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 78 | 25 | Eat App Partner API +53 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 59 | 5 | Eat App Partner API +54 |
| Agent ergonomics | 13%16.2 | 66 | 0 | Eat App Partner API +66 |
| Security & auth | 14%17.5 | 43 | 0 | Eat App Partner API +43 |
| Payments & pricing | 10%12.5 | 15 | 0 | Eat App Partner API +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 40 | 23 | Eat App Partner API +17 |
| Transparency & trust | 7%8.8 | 52 | 52 | even |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 53.4/100 | F 12.4/100 |
Facts side by side
| Fact | Eat App Partner API | Tock |
|---|---|---|
| Kind | HTTP API | Platform |
| Vendor | Eat App (EAT APPLICATION DMCC) | Tock (American Express) |
| Hosted endpoint | https://api.eatapp.co/partners/v2 | no (local only) |
| Transports | HTTP | |
| Auth | OAuth or key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements | Proprietary service under the Tock Terms of Use (effective 12 February 2026) and merchant terms |
| Read-only variant documented | yes | no |
| llms.txt | no | no |
| Last release | 2026-10-13 | none |
| Terms last updated | 2025-09-10 | 2026-02-12 |
| Privacy policy last updated | no date given | 2025-11-24 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
Verdicts
Eat App Partner API
A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.
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
Eat App Partner API
- Send a unique idempotency_token with each new booking so a retry returns the first result
- Use POST /partners/v2/availability/range, not the legacy availability endpoint
- Keep include_tables ranges to 24 hours or less and pass covers with it
- Stay under 60 requests a minute and wait for the next minute after a 429
- Cancel by PATCH with status canceled, after which the reservation can no longer change
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, Eat App Partner API or Tock?
Eat App Partner API scores 53.4 (D) on agent readiness against Tock's 12.4 (F), and leads in 6 of 7 scored categories.
Can an agent call Eat App Partner API and Tock without installing anything?
Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2. No hosted endpoint is listed for Tock.
Other comparisons with Eat App Partner API or Tock
- Chope vs Eat App Partner API
- Chope vs Tock
- Eat App Partner API vs OpenTable APIs
- Eat App Partner API vs Resy
- Eat App Partner API vs SevenRooms
- Eat App Partner API vs TableCheck API
- Eat App Partner API vs TheFork B2B API
- OpenTable APIs vs Tock
- Resy vs Tock
- TableCheck API vs Tock
- TheFork B2B API vs Tock
- Eat App Partner API vs Square Appointments (Bookings API)
- SevenRooms vs Tock
- Square Appointments (Bookings API) vs Tock
Machine-readable
- This page as Markdown
/compare/eat-app-vs-tock.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/eat-app.json·/api/v1/tools/tock.json - From a terminal
anchor compare eat-app tock(the CLI) - Over MCP
compare_tools {"a": "eat-app", "b": "tock"}at/mcp, no key