# Eat App Partner API vs Tock

> Eat App Partner scores 53.4 (D) to Tock's 12.4 (F) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.

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

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.

- Eat App Partner API: grade D, 53.4/100, rank #752 of 1076. Markdown https://www.anchorterminal.com/tools/eat-app.md · JSON https://www.anchorterminal.com/api/v1/tools/eat-app.json
- Tock: grade F, 12.4/100, rank #1062 of 1076. Markdown https://www.anchorterminal.com/tools/tock.md · JSON https://www.anchorterminal.com/api/v1/tools/tock.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

### Eat App Partner API (D)

Good 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)

Good for: Restaurants and wineries taking reservations and experience bookings, and for diners booking in person.

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 | Eat App Partner API | Tock | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 78 | 25 | Eat App Partner API +53 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 59 | 5 | Eat App Partner API +54 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 0 | Eat App Partner API +66 |
| Security & auth | 14% (17.5 this run) | 43 | 0 | Eat App Partner API +43 |
| Payments & pricing | 10% (12.5 this run) | 15 | 0 | Eat App Partner API +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 40 | 23 | Eat App Partner API +17 |
| Transparency & trust | 7% (8.8 this run) | 52 | 52 | even |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **53.4 · D** | **12.4 · F** | |

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

1. Send a unique idempotency_token with each new booking so a retry returns the first result
2. Use POST /partners/v2/availability/range, not the legacy availability endpoint
3. Keep include_tables ranges to 24 hours or less and pass covers with it
4. Stay under 60 requests a minute and wait for the next minute after a 429
5. Cancel by PATCH with status canceled, after which the reservation can no longer change

### Tock

1. Don't plan to call Tock from another agent. Hand the booking to the person on exploretock.com or in the Resy app
2. 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.


## For agents

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

## Other comparisons with Eat App Partner API or Tock

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