Write a review

Head to head · Booking availability · October 2026 research run

OpenTable APIs vs TableCheck API

TableCheck API scores 57.1 (C) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 6 of 7 scored categories. OpenTable APIs leads on payments & pricing. Both do booking availability.

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

OpenTable APIsOpenTable · HTTP API E38.6/100#994 of 1076 TableCheck APITableCheck Inc. · HTTP API C57.1/100#661 of 1076

Which one, for what

OpenTable APIs E

Best for Approved affiliates, restaurant groups and voice AI vendors that need to book into OpenTable restaurants.

Ahead on

  • Payments & pricing, 5 against 0

Watch for

Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials

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
  • Schema & documentation, 77 against 61
  • Security & auth, 46 against 33
  • Maintenance & community, 35 against 5
  • Transparency & trust, 66 against 42

Watch for

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

Score by category

CategoryWeight this runOpenTable APIsTableCheck APIEdge
Reliability16%203580TableCheck API +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26177TableCheck API +16
Agent ergonomics13%16.26972TableCheck API +3
Security & auth14%17.53346TableCheck API +13
Payments & pricing10%12.550OpenTable APIs +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8535TableCheck API +30
Transparency & trust7%8.84266TableCheck API +24
Negative events≤1500
TotalE 38.6/100C 57.1/100

Facts side by side

FactOpenTable APIsTableCheck API
KindHTTP APIHTTP API
VendorOpenTableTableCheck Inc.
Hosted endpointhttps://platform.opentable.comhttps://api.tablecheck.com/api/
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthAPI key
PricingYour planPaid
x402nono
LicenceProprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentationProprietary service under the TableCheck API Terms of Service
Tools exposednone20
Read-only variant documentednoyes
llms.txtnono
Terms last updatedcouldn't be read2022-10-11
Privacy policy last updatedcouldn't be read2016-12-14
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text

Verdicts

OpenTable APIs

The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.

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.

Before you call either

OpenTable APIs

  1. Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes
  2. Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated
  3. Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner
  4. Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel
  5. Ask the OpenTable representative for the rate limit of each endpoint before going live

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

Questions

Which is better for AI agents, OpenTable APIs or TableCheck API?

TableCheck API scores 57.1 (C) on agent readiness against OpenTable APIs's 38.6 (E), and leads in 6 of 7 scored categories. OpenTable APIs leads on payments & pricing.

Do OpenTable APIs and TableCheck API need an API key?

OpenTable APIs uses an OAuth sign-in. TableCheck API needs an API key.

Can an agent call OpenTable APIs and TableCheck API without installing anything?

Yes. OpenTable APIs has a hosted endpoint at https://platform.opentable.com and TableCheck API at https://api.tablecheck.com/api/.

Other comparisons with OpenTable APIs or TableCheck 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