# Resy vs TheFork B2B API

> TheFork B2B scores 43.6 (E) 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/resy-vs-thefork
- Markdown: https://www.anchorterminal.com/compare/resy-vs-thefork.md (~2,000 tokens)
- Slim: https://www.anchorterminal.com/compare/resy-vs-thefork.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/resy-vs-thefork.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

TheFork B2B API scores 43.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 restaurant reservations.

- 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
- TheFork B2B API: grade E, 43.6/100, rank #951 of 1076. Markdown https://www.anchorterminal.com/tools/thefork.md · JSON https://www.anchorterminal.com/api/v1/tools/thefork.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

### Resy (F)

Good for: Diners booking in person through the app.

Ahead on:
- Maintenance & community, 25 against 15

Watch for: No public API or MCP server an outside agent can call. The Amex dining MCP endpoint takes only pre-registered OAuth clients

### TheFork B2B API (E)

Good for: CRM, PMS and AI phone-agent vendors and restaurant groups that run on TheFork Manager, mainly in Europe.

Ahead on:
- Reliability, 35 against 25
- Schema & documentation, 87 against 0
- Agent ergonomics, 56 against 0
- Security & auth, 42 against 3
- Payments & pricing, 5 against 0
- Transparency & trust, 47 against 30

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: Venue-side only. Credentials cover the restaurants that granted access, and no endpoint lists restaurants


## Score by category

| Category | Weight | Resy | TheFork B2B API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 25 | 35 | TheFork B2B API +10 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 0 | 87 | TheFork B2B API +87 |
| Agent ergonomics | 13% (16.2 this run) | 0 | 56 | TheFork B2B API +56 |
| Security & auth | 14% (17.5 this run) | 3 | 42 | TheFork B2B API +39 |
| Payments & pricing | 10% (12.5 this run) | 0 | 5 | TheFork B2B API +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 25 | 15 | Resy +10 |
| Transparency & trust | 7% (8.8 this run) | 30 | 47 | TheFork B2B API +17 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **10.3 · F** | **43.6 · E** | |

## Facts side by side

| Fact | Resy | TheFork B2B API |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Resy (American Express) | TheFork (La Fourchette SAS) |
| Hosted endpoint | no (local only) | `https://api.thefork.io/manager` |
| Transports |  | HTTP |
| Auth | OAuth | OAuth |
| Pricing | Paid | Your plan |
| x402 | no | no |
| Licence | Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock | Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Terms last updated | no document linked |  |
| Privacy policy last updated | couldn't be read | no document linked |
| Customer content may train models |  |  |
| Terms restrict automated access |  |  |
| Terms restrict benchmarking |  |  |
| Terms or service can change without notice |  |  |
| Arbitration or class-action waiver |  |  |

## Verdicts

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

**TheFork B2B API.** A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices.

## Before you call either

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

### TheFork B2B API

1. Read hasPaymentGuaranteeRequirement in the timeslots response before booking, since the API cannot take a card
2. Check the status field after creating a reservation and treat REQUESTED as unconfirmed
3. Send the timeslot datetime unchanged as mealDate, because times are the restaurant's local time
4. Check for an existing reservation before retrying a failed POST, as no idempotency key exists and 409 signals DOUBLE_BOOKING
5. Cache the access token for its 8,600 seconds and do not request a new one while it is valid

## Questions

### Which is better for AI agents, Resy or TheFork B2B API?

TheFork B2B API scores 43.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 Resy and TheFork B2B API without installing anything?

No hosted endpoint is listed for Resy. TheFork B2B API has a hosted endpoint at https://api.thefork.io/manager.


## For agents

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

## Other comparisons with Resy or TheFork B2B API

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