# Eat App Partner API vs Resy

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

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

Eat App Partner API scores 53.4 (D) on agent readiness against Resy's 10.3 (F), and leads in every scored category. 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
- 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

### 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 0
- Agent ergonomics, 66 against 0
- Security & auth, 43 against 3
- Payments & pricing, 15 against 0
- Maintenance & community, 40 against 25
- Transparency & trust, 52 against 30

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

### Resy (F)

Good for: Diners booking in person through the app.

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 | Eat App Partner API | Resy | 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 | 0 | Eat App Partner API +59 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 0 | Eat App Partner API +66 |
| Security & auth | 14% (17.5 this run) | 43 | 3 | Eat App Partner API +40 |
| 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 | 25 | Eat App Partner API +15 |
| Transparency & trust | 7% (8.8 this run) | 52 | 30 | Eat App Partner API +22 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **53.4 · D** | **10.3 · F** | |

## Facts side by side

| Fact | Eat App Partner API | Resy |
| --- | --- | --- |
| Kind | HTTP API | Platform |
| Vendor | Eat App (EAT APPLICATION DMCC) | Resy (American Express) |
| Hosted endpoint | `https://api.eatapp.co/partners/v2` | no (local only) |
| Transports | HTTP |  |
| Auth | OAuth or key | OAuth |
| 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. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock |
| Read-only variant documented | yes | no |
| llms.txt | no | no |
| Last release | 2026-10-13 | none |
| Terms last updated | 2025-09-10 | no document linked |
| Privacy policy last updated | no date given | couldn't be read |
| Customer content may train models | not found in the text |  |
| Terms restrict automated access | not found in the text |  |
| Terms restrict benchmarking | yes |  |
| Terms or service can change without notice | not found in the text |  |
| Arbitration or class-action waiver | not found in the text |  |

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

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

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

### 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, Eat App Partner API or Resy?

Eat App Partner API scores 53.4 (D) on agent readiness against Resy's 10.3 (F), and leads in every scored category.

### Can an agent call Eat App Partner API and Resy without installing anything?

Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2. No hosted endpoint is listed for Resy.


## For agents

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

## Other comparisons with Eat App Partner API or Resy

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