# Eat App Partner API vs TableCheck API

> TableCheck scores 57.1 (C) to Eat App Partner's 53.4 (D) for restaurant reservations. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/eat-app-vs-tablecheck
- Markdown: https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/eat-app-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
- Licence: CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.
- Updated: 2026-10-15

TableCheck API scores 57.1 (C) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 5 of 7 scored categories. Eat App Partner API leads on payments & pricing and maintenance & community. Both do restaurant reservations.

- Eat App Partner API: grade D, 53.4/100, rank #759 of 1094. Markdown https://www.anchorterminal.com/tools/eat-app.md · JSON https://www.anchorterminal.com/api/v1/tools/eat-app.json
- TableCheck API: grade C, 57.1/100, rank #666 of 1094. 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

### Eat App Partner API (D)

Good for: Booking channels and concierge services that want to book into Eat App restaurants, and for restaurants that want an assistant to read their data.

Ahead on:
- Payments & pricing, 15 against 0
- Maintenance & community, 40 against 35

Watch for: A booking channel can book only at restaurants whose partnership Eat App has activated

### TableCheck API (C)

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

Ahead on:
- Schema & documentation, 77 against 59
- Agent ergonomics, 72 against 66
- Transparency & trust, 66 against 52

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


## Score by category

| Category | Weight | Eat App Partner API | TableCheck API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 78 | 80 | TableCheck API +2 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 59 | 77 | TableCheck API +18 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 72 | TableCheck API +6 |
| Security & auth | 14% (17.5 this run) | 43 | 46 | TableCheck API +3 |
| Payments & pricing | 10% (12.5 this run) | 15 | 0 | Eat App Partner API +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 40 | 35 | Eat App Partner API +5 |
| Transparency & trust | 7% (8.8 this run) | 52 | 66 | TableCheck API +14 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **53.4 · D** | **57.1 · C** | |

## Facts side by side

| Fact | Eat App Partner API | TableCheck API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Eat App (EAT APPLICATION DMCC) | TableCheck Inc. |
| Hosted endpoint | `https://api.eatapp.co/partners/v2` | `https://api.tablecheck.com/api/` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under Eat App's terms of service (effective 10 September 2025) and partner agreements | Proprietary service under the TableCheck API Terms of Service |
| Tools exposed | none | 20 |
| Read-only variant documented | yes | yes |
| llms.txt | no | no |
| Last release | 2026-10-13 | none |
| Terms last updated | 2025-09-10 | 2022-10-11 |
| Privacy policy last updated | no date given | 2016-12-14 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |

## Verdicts

**Eat App Partner API.** A diner-side Partner API with idempotent booking, a stated rate limit, per-API status monitoring and a changelog updated on 13 October 2026, plus a read-only MCP server for restaurants. Partnerships are activated restaurant by restaurant, API access is priced through sales, and the docs are a Postman collection without OpenAPI or llms.txt.

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

### Eat App Partner API

1. Send a unique idempotency_token with each new booking so a retry returns the first result
2. Use POST /partners/v2/availability/range, not the legacy availability endpoint
3. Keep include_tables ranges to 24 hours or less and pass covers with it
4. Stay under 60 requests a minute and wait for the next minute after a 429
5. Cancel by PATCH with status canceled, after which the reservation can no longer change

### 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, Eat App Partner API or TableCheck API?

TableCheck API scores 57.1 (C) on agent readiness against Eat App Partner API's 53.4 (D), and leads in 5 of 7 scored categories. Eat App Partner API leads on payments & pricing and maintenance & community.

### Do Eat App Partner API and TableCheck API need an API key?

Eat App Partner API takes an API key or an OAuth sign-in. TableCheck API needs an API key.

### Can an agent call Eat App Partner API and TableCheck API without installing anything?

Yes. Eat App Partner API has a hosted endpoint at https://api.eatapp.co/partners/v2 and TableCheck API at https://api.tablecheck.com/api/.


## For agents

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

## Other comparisons with Eat App Partner API or TableCheck API

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