# TableCheck API (slim)

> TableCheck is a restaurant reservation and guest management platform used mainly in Japan and Asia. Its API components cover availability, booking, CRM, POS and distribution to booking sites, with an MCP server for merchants.

- Full: https://www.anchorterminal.com/tools/tablecheck.md (~6,150 tokens) · this version ~1,480 tokens · JSON https://www.anchorterminal.com/tools/tablecheck.json · canonical https://www.anchorterminal.com/tools/tablecheck
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-14

**C · 57.1/100 · rank #661 of 1076 · #2 in Restaurant & local bookings · not agent-ready · confidence medium**


Assessment: 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.

## Facts

- Kind: HTTP API · vendor: TableCheck Inc. · category: Restaurant & local bookings · legal entity: TableCheck Inc. · provenance 86/100
- Endpoint: `https://api.tablecheck.com/api/` (HTTP, Streamable HTTP)
- Auth: API key · pricing: Paid · x402: no · licence: Proprietary service under the TableCheck API Terms of Service
- Probe metrics: not measured yet (probes haven't run)
- Surface graded: The REST API components at https://api.tablecheck.com/api/ and MCP for Merchants v1, read from the Confluence API space, the Booking v1 OpenAPI file and the status page on 14 October 2026
- Acts for: Both. Availability, Distribution and Web Booking serve diner-facing booking and listing sites. Booking, CRM, POS and the MCP serve the venue
- Booking cycle: Availability API for dates and times, a 5-minute blockage, POST /reservations, PUT to amend and PUT /reservations/{id}/cancel, with Sync webhooks for changes
- Payments and deposits: Booking v1 and Distribution v1 don't take payments. Web Booking v1 redirects to TableCheck's hosted page when payment is needed
- MCP server: Streamable HTTP at /api/mcp_merchant/v1, staging and production, bearer key. 20 tools, read-only keys recommended, personal data omitted by default. Under development
- Rate limits: 10,000 requests per 5 minutes per component. 429 when exceeded, then wait for the next window
- Coverage: TableCheck says it is used in over 3,000 restaurants in over 20 countries

- Scores: Reliability 80, Performance pending, Schema & documentation 77, Agent ergonomics 72, Security & auth 46, Payments & pricing 0, Task success pending, Maintenance & community 35, Transparency & trust 66 · total over the 7 assessed categories
- Why: Reliability, Graded on the hosted REST API and the MCP for Merchants endpoint. · Schema & documentation, Each component serves an OpenAPI 3.0 YAML at its /docs URL, for example Booking v1 at https://api.tablecheck.com/api/booking/v1/docs (25). · Agent ergonomics, The MCP server has 20 tools, filtered to the components a key holds, and returns compact projections with personal data omitted unless asked… · Security & auth, One `secret_key` per environment issued by the API team and rolled on request, with access limited to the components and venues approved for… · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, Read for a closed service. · Transparency & trust, Closed service under published TableCheck API Terms of Service (enacted 10 December 2018) with TableCheck, Inc.
- Sources: 14, open questions: 6, both in the full twin
- Capabilities: booking.availability, booking.reservations, booking.venue, booking.orders
- JSON: https://www.anchorterminal.com/api/v1/tools/tablecheck.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/tablecheck.svg` or a link to https://www.anchorterminal.com/tools/tablecheck from a page on tablecheck.com or one of its subdomains, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

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

## Connect

```bash
claude mcp add --transport http tablecheck \
  https://api.staging-qa.tablecheck.com/api/mcp_merchant/v1 \
  --header "Authorization: Bearer $TABLECHECK_API_KEY"
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/tablecheck

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Eat App Partner API | D | 53.4 | booking.reservations, booking.availability, booking.venue | https://www.anchorterminal.com/tools/eat-app.min.md |
| TheFork B2B API | E | 43.6 | booking.reservations, booking.availability, booking.venue | https://www.anchorterminal.com/tools/thefork.min.md |
| OpenTable APIs | E | 38.6 | booking.availability, booking.reservations, booking.venue | https://www.anchorterminal.com/tools/opentable.min.md |
| SevenRooms | F | 17.7 | booking.venue, booking.reservations, booking.availability | https://www.anchorterminal.com/tools/sevenrooms.min.md |
| Resy | F | 10.3 | booking.reservations, booking.availability, booking.venue | https://www.anchorterminal.com/tools/resy.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)