Head to head · Restaurant reservations · October 2026 research run
TheFork B2B API vs Tock
TheFork B2B API scores 43.6 (E) on agent readiness against Tock's 12.4 (F), and leads in 5 of 7 scored categories. Tock leads on maintenance & community and transparency & trust. Both do restaurant reservations.
Best restaurant reservation and local appointment APIs for AI agents · All 36 bookings comparisons
Which one, for what
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 5
- Agent ergonomics, 56 against 0
- Security & auth, 42 against 0
- Payments & pricing, 5 against 0
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
Tock F
Best for Restaurants and wineries taking reservations and experience bookings, and for diners booking in person.
Ahead on
- Maintenance & community, 23 against 15
- Transparency & trust, 52 against 47
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 | TheFork B2B API | Tock | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 35 | 25 | TheFork B2B API +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 87 | 5 | TheFork B2B API +82 |
| Agent ergonomics | 13%16.2 | 56 | 0 | TheFork B2B API +56 |
| Security & auth | 14%17.5 | 42 | 0 | TheFork B2B API +42 |
| Payments & pricing | 10%12.5 | 5 | 0 | TheFork B2B API +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 15 | 23 | Tock +8 |
| Transparency & trust | 7%8.8 | 47 | 52 | Tock +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 43.6/100 | F 12.4/100 |
Facts side by side
| Fact | TheFork B2B API | Tock |
|---|---|---|
| Kind | HTTP API | Platform |
| Vendor | TheFork (La Fourchette SAS) | Tock (American Express) |
| Hosted endpoint | https://api.thefork.io/manager | no (local only) |
| Transports | HTTP | |
| Auth | OAuth | API key |
| Pricing | Your plan | Paid |
| x402 | no | no |
| Licence | Proprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork | Proprietary service under the Tock Terms of Use (effective 12 February 2026) and merchant terms |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Terms last updated | 2026-02-12 | |
| Privacy policy last updated | no document linked | 2025-11-24 |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | yes | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | yes | |
| Arbitration or class-action waiver | yes |
Verdicts
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.
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
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
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, TheFork B2B API or Tock?
TheFork B2B API scores 43.6 (E) on agent readiness against Tock's 12.4 (F), and leads in 5 of 7 scored categories. Tock leads on maintenance & community and transparency & trust.
Can an agent call TheFork B2B API and Tock without installing anything?
TheFork B2B API has a hosted endpoint at https://api.thefork.io/manager. No hosted endpoint is listed for Tock.
Other comparisons with TheFork B2B API or Tock
- Chope vs TheFork B2B API
- Chope vs Tock
- Eat App Partner API vs TheFork B2B API
- Eat App Partner API vs Tock
- OpenTable APIs vs Tock
- Resy vs TheFork B2B API
- Resy vs Tock
- TableCheck API vs Tock
- OpenTable APIs vs TheFork B2B API
- Square Appointments (Bookings API) vs TheFork B2B API
- TableCheck API vs TheFork B2B API
- SevenRooms vs TheFork B2B API
- SevenRooms vs Tock
- Square Appointments (Bookings API) vs Tock
Machine-readable
- This page as Markdown
/compare/thefork-vs-tock.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/thefork.json·/api/v1/tools/tock.json - From a terminal
anchor compare thefork tock(the CLI) - Over MCP
compare_tools {"a": "thefork", "b": "tock"}at/mcp, no key