# Resy vs TableCheck API

> TableCheck scores 57.1 (C) 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-tablecheck
- Markdown: https://www.anchorterminal.com/compare/resy-vs-tablecheck.md (~2,000 tokens)
- Slim: https://www.anchorterminal.com/compare/resy-vs-tablecheck.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/resy-vs-tablecheck.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

TableCheck API scores 57.1 (C) on agent readiness against Resy's 10.3 (F), and leads in 6 of 7 scored categories. 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
- TableCheck API: grade C, 57.1/100, rank #661 of 1076. Markdown https://www.anchorterminal.com/tools/tablecheck.md · JSON https://www.anchorterminal.com/api/v1/tools/tablecheck.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.

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

### TableCheck API (C)

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

Ahead on:
- Reliability, 80 against 25
- Schema & documentation, 77 against 0
- Agent ergonomics, 72 against 0
- Security & auth, 46 against 3
- Maintenance & community, 35 against 25
- Transparency & trust, 66 against 30

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

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


## Score by category

| Category | Weight | Resy | TableCheck API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 25 | 80 | TableCheck API +55 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 0 | 77 | TableCheck API +77 |
| Agent ergonomics | 13% (16.2 this run) | 0 | 72 | TableCheck API +72 |
| Security & auth | 14% (17.5 this run) | 3 | 46 | TableCheck API +43 |
| Payments & pricing | 10% (12.5 this run) | 0 | 0 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 25 | 35 | TableCheck API +10 |
| Transparency & trust | 7% (8.8 this run) | 30 | 66 | TableCheck API +36 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **10.3 · F** | **57.1 · C** | |

## Facts side by side

| Fact | Resy | TableCheck API |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Resy (American Express) | TableCheck Inc. |
| Hosted endpoint | no (local only) | `https://api.tablecheck.com/api/` |
| Transports |  | HTTP, Streamable HTTP |
| Auth | OAuth | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock | Proprietary service under the TableCheck API Terms of Service |
| Tools exposed | none | 20 |
| Read-only variant documented | no | yes |
| llms.txt | no | no |
| Terms last updated | no document linked | 2022-10-11 |
| Privacy policy last updated | couldn't be read | 2016-12-14 |
| Customer content may train models |  | not found in the text |
| Terms restrict automated access |  | not found in the text |
| Terms restrict benchmarking |  | yes |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | not found in the text |

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

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

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

### 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, Resy or TableCheck API?

TableCheck API scores 57.1 (C) on agent readiness against Resy's 10.3 (F), and leads in 6 of 7 scored categories.

### Can an agent call Resy and TableCheck API without installing anything?

No hosted endpoint is listed for Resy. TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/.


## For agents

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

## Other comparisons with Resy or TableCheck API

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