Write a review

Head to head · Booking availability · October 2026 research run

TableCheck API vs TheFork B2B API

TableCheck API scores 57.1 (C) on agent readiness against TheFork B2B API's 43.6 (E), and leads in 5 of 7 scored categories. TheFork B2B API leads on schema & documentation and payments & pricing. Both do booking availability.

Best restaurant reservation and local appointment APIs for AI agents · All 36 bookings comparisons

TableCheck APITableCheck Inc. · HTTP API C57.1/100#661 of 1076 TheFork B2B APITheFork (La Fourchette SAS) · HTTP API E43.6/100#951 of 1076

Which one, for what

TableCheck API C

Best for Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.

Ahead on

  • Reliability, 80 against 35
  • Agent ergonomics, 72 against 56
  • Maintenance & community, 35 against 15
  • Transparency & trust, 66 against 47

Watch for

Access needs an emailed application, case-by-case approval and fees quoted privately

TheFork B2B API E

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

Ahead on

  • Schema & documentation, 87 against 77
  • Payments & pricing, 5 against 0

Watch for

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

Score by category

CategoryWeight this runTableCheck APITheFork B2B APIEdge
Reliability16%208035TableCheck API +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27787TheFork B2B API +10
Agent ergonomics13%16.27256TableCheck API +16
Security & auth14%17.54642TableCheck API +4
Payments & pricing10%12.505TheFork B2B API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83515TableCheck API +20
Transparency & trust7%8.86647TableCheck API +19
Negative events≤1500
TotalC 57.1/100E 43.6/100

Facts side by side

FactTableCheck APITheFork B2B API
KindHTTP APIHTTP API
VendorTableCheck Inc.TheFork (La Fourchette SAS)
Hosted endpointhttps://api.tablecheck.com/api/https://api.thefork.io/manager
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyOAuth
PricingPaidYour plan
x402nono
LicenceProprietary service under the TableCheck API Terms of ServiceProprietary service under TheFork Partners API Terms of Use (La Fourchette SAS) and any core agreement with TheFork
Tools exposed20none
Read-only variant documentedyesyes
llms.txtnoyes
Terms last updated2022-10-11
Privacy policy last updated2016-12-14no document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingyes
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text

Verdicts

TableCheck API

TableCheck publishes OpenAPI specs for availability, booking, CRM and POS components and a merchant MCP server with read-only keys, idempotent writes and personal data hidden by default. Access is by email application with case-by-case approval and unpublished fees, the MCP server is still under development, and no audit log or dated changelog was found.

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

TableCheck API

  1. Decide which side you act for. Distribution and Web Booking serve diner-facing platforms, while Booking, CRM, POS and the MCP serve the venue
  2. Ask the operator for a read-only key before using the MCP, as TableCheck recommends, and avoid cancellations through it
  3. Call hold_table (MCP) or POST /blockages (REST) before booking, since availability is a snapshot and a blockage expires in 5 minutes
  4. Send dates as YYYY-MM-DD and convert the UTC times returned to the venue's time zone from list_shops
  5. Stay under 10,000 requests per 5 minutes per component and wait for the next window after a 429

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, TableCheck API or TheFork B2B API?

TableCheck API scores 57.1 (C) on agent readiness against TheFork B2B API's 43.6 (E), and leads in 5 of 7 scored categories. TheFork B2B API leads on schema & documentation and payments & pricing.

Do TableCheck API and TheFork B2B API need an API key?

TableCheck API needs an API key. TheFork B2B API uses an OAuth sign-in.

Can an agent call TableCheck API and TheFork B2B API without installing anything?

Yes. TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/ and TheFork B2B API at https://api.thefork.io/manager.

Other comparisons with TableCheck API or TheFork B2B API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report