Head to head · Restaurant reservations · October 2026 research run
Resy vs 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. Both do restaurant reservations.
Best restaurant reservation and local appointment APIs for AI agents · All 36 bookings comparisons
Which one, for what
Resy F
Best 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
Best 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 this run | Resy | TheFork B2B API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 25 | 35 | TheFork B2B API +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 0 | 87 | TheFork B2B API +87 |
| Agent ergonomics | 13%16.2 | 0 | 56 | TheFork B2B API +56 |
| Security & auth | 14%17.5 | 3 | 42 | TheFork B2B API +39 |
| Payments & pricing | 10%12.5 | 0 | 5 | TheFork B2B API +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 25 | 15 | Resy +10 |
| Transparency & trust | 7%8.8 | 30 | 47 | TheFork B2B API +17 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 10.3/100 | E 43.6/100 |
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
- 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
- Do not automate the Resy website or app, since Resy runs a bot-detection programme against automated booking
TheFork B2B API
- Read hasPaymentGuaranteeRequirement in the timeslots response before booking, since the API cannot take a card
- Check the status field after creating a reservation and treat REQUESTED as unconfirmed
- Send the timeslot datetime unchanged as mealDate, because times are the restaurant's local time
- Check for an existing reservation before retrying a failed POST, as no idempotency key exists and 409 signals DOUBLE_BOOKING
- 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.
Other comparisons with Resy or TheFork B2B API
- Chope vs Resy
- Chope vs TheFork B2B API
- Eat App Partner API vs Resy
- Eat App Partner API vs TheFork B2B API
- Resy vs SevenRooms
- Resy vs TableCheck API
- Resy vs Tock
- TheFork B2B API vs Tock
- OpenTable APIs vs Resy
- OpenTable APIs vs TheFork B2B API
- Resy vs Square Appointments (Bookings API)
- Square Appointments (Bookings API) vs TheFork B2B API
- TableCheck API vs TheFork B2B API
- SevenRooms vs TheFork B2B API
Machine-readable
- This page as Markdown
/compare/resy-vs-thefork.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/resy.json·/api/v1/tools/thefork.json - From a terminal
anchor compare resy thefork(the CLI) - Over MCP
compare_tools {"a": "resy", "b": "thefork"}at/mcp, no key