# TableCheck API > 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. - Canonical: https://www.anchorterminal.com/tools/tablecheck - Markdown: https://www.anchorterminal.com/tools/tablecheck.md (~6,150 tokens) - Slim: https://www.anchorterminal.com/tools/tablecheck.min.md (~1,480 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/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 ## Overview **Grade 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 | Field | Value | | --- | --- | | Vendor | TableCheck Inc. (https://www.tablecheck.com) | | Kind | HTTP API | | Category | Restaurant & local bookings (https://www.anchorterminal.com/categories/local-bookings) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://api.tablecheck.com/api/` | | Auth | API key · Sales-led. Email api@tablecheck.com, complete the API Portal questionnaire and accept the API terms. Each approved request gets one `secret_key` per environment in the `Authorization` header, limited to the approved components and, for aggregators, approved venues. The API team rolls keys on request. The MCP server needs the `mcp_merchant` component added to a key (https://tablecheck.atlassian.net/wiki/spaces/API/pages/44630975). | | Pricing | Paid (Paid) · No public price. The access page says "Fees may vary" and pricing is given during the application. No free tier. Test accounts and test data are prepared on request (https://tablecheck.atlassian.net/wiki/spaces/API/pages/43909423, checked 2026-10-14). | | x402 | No · No x402, MPP or L402 in the API documentation or the OpenAPI files read (checked 2026-10-14). | | Licence | Proprietary service under the TableCheck API Terms of Service | | Tools exposed | 20 | | Docs | https://tablecheck.atlassian.net/wiki/spaces/API/overview | | llms.txt | not found | | 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 | | Capabilities | booking.availability, booking.reservations, booking.venue, booking.orders | | Tags | hosted, closed-source, rest, openapi, mcp, sales-led, status-page, diner-side, venue-side | | JSON | https://www.anchorterminal.com/api/v1/tools/tablecheck.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-14 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 80 | 16.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 77 | 12.5 | | Agent ergonomics | 13% | 16.2 | 72 | 11.7 | | Security & auth | 14% | 17.5 | 46 | 8.1 | | Payments & pricing | 10% | 12.5 | 0 | 0.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 35 | 3.1 | | Transparency & trust (editorial 45, provenance 86) | 7% | 8.8 | 66 | 5.8 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **57.1 → C** | ### Why each score - Reliability 80: Graded on the hosted REST API and the MCP for Merchants endpoint. Statuspage site at tablecheck.statuspage.io with a "TableCheck Third Party API" component (20). No incident in the 90 days to 14 October 2026. The most recent posted incident is from 22 February 2023, so the page may be little used, which we note without deducting (30). 10,000 requests per 5 minutes for each API component (15). 429 is documented with an instruction to wait for the next 5-minute period, without Retry-After. The REST booking flow uses a 5-minute table blockage before a reservation, and MCP writes take an idempotency key, but REST POST /reservations has none (7). No SLA, and the rate-limit page says the limit is not a service level commitment (0). Availability and Booking v1 are live. MCP for Merchants is marked under development (8). Total 80. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 77: 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). No llms.txt or Markdown docs. The guides live on a Confluence site (0). Guide pages name the target audience, compare the three booking APIs and say what each is not for, and the MCP page lists what it should not be used for (17). The Booking spec has 27 enums and required fields (12). The Booking spec documents 51 4xx responses with examples, and the guides give request examples (13). Major versions in the path, a written change and deprecation policy and an announcements page, but no dated changelog (10). Total 77. - Agent ergonomics 72: The MCP server has 20 tools, filtered to the components a key holds, and returns compact projections with personal data omitted unless asked (15 + 5). REST lists filter by date, venue and guest, and MCP results are capped (15). 401 and 403 are explained, and the MCP validates dates strictly so a model can correct the call (16). MCP write tools take `idempotency_key` and carry destructiveHint. REST booking has no idempotency key but a blockage hold (16). A JavaScript Booking Form SDK exists, with no server SDKs (5). Total 72. - Security & auth 46: One `secret_key` per environment issued by the API team and rolled on request, with access limited to the components and venues approved for the key. No self-serve rotation or OAuth (20). Keys can be set to read-only for the MCP, write tools are marked destructive, and guest names, phones and emails are omitted from MCP results unless requested (17). The MCP page states its trust assumptions (human in the loop, the key as the boundary, personal data redacted) but gives no prompt-injection guidance for guest-written notes (6). No audit log found (0). www.tablecheck.com/.well-known/security.txt returns an HTML page, not a security.txt. The trust centre at trust.tablecheck.com renders with JavaScript only and was not read (3). Total 46. - Payments & pricing 0: No x402, MPP or L402 (0). "Fees may vary", with pricing given during the application (0). No free tier. Test accounts and data are prepared on request (0). Access starts with an email to api@tablecheck.com and a case-by-case review (0). Total 0. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 35: Read for a closed service. The MCP for Merchants page was last edited on 20 September 2026, and Messaging v1 and Custom Email Domain v1 in July 2026, which we count as the latest dated changes (30). No dated changelog with three entries in 90 days (0). Support by email (api@tablecheck.com, support@tablecheck.com), with no public issue tracker or forum (5). No server SDKs, and the MCP server is not in the official MCP registry (0). No package to judge (0). Total 35. - Transparency & trust 66: Closed service under published TableCheck API Terms of Service (enacted 10 December 2018) with TableCheck, Inc. (15). The privacy policy, revised 14 September 2026, says most information is retained indefinitely unless law or a deletion request requires otherwise (10). A written API change policy promises backwards compatibility within a major version and a deprecation process, and the tablesolution.com URL retirement was announced with dates (3 June and 2 October 2026) (18). Third-party processors are not named and no data locations are given (2). Total 45. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (16 items): https://www.anchorterminal.com/fixes/tablecheck.md (JSON https://www.anchorterminal.com/fixes/tablecheck.json) ### What we couldn't check - unchecked: the trust centre at trust.tablecheck.com, which renders with JavaScript only - The status page shows no incident since 22 February 2023, which may mean it is rarely updated - The MCP page's stdio bridge example uses https://api.staging-qa.tablecheck.com/api/mcp/v1, while the endpoint given elsewhere on the page is /api/mcp_merchant/v1 - The MCP tool list was read from the docs page. No call was made to the live MCP server - Only Booking v1's OpenAPI file was read in full. The other components' specs were not fetched - Acts for both sides. Booking v1 is limited to first-party users (venue operators or their integration partners) ### Sources - API documentation home: (seen 2026-10-14) - Getting Started: (seen 2026-10-14) - Booking APIs comparison: (seen 2026-10-14) - Booking v1: (seen 2026-10-14) - Availability v1: (seen 2026-10-14) - MCP for Merchants v1: (seen 2026-10-14) - Rate Limits & Cutoff: (seen 2026-10-14) - API Change Policy: (seen 2026-10-14) - API Announcements: (seen 2026-10-14) - API Terms of Service: (seen 2026-10-14) - Booking v1 OpenAPI: (seen 2026-10-14) - status components and incidents: (seen 2026-10-14) - privacy policy: (seen 2026-10-14) - wiki page list: (seen 2026-10-14) ## Who's behind it (provenance 86/100, checked 2026-10-14) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | TableCheck Inc. | 20/20 | | Domain age | tablecheck.com, registered 1998-07-01 (28 years) | 15/15 | | Endpoint on the vendor's domain | api.tablecheck.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | tablecheck.statuspage.io | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The API Terms of Service (enacted 10 December 2018) are with TableCheck, Inc. outside Mainland China and its designated entity inside it. The privacy policy (revised 14 September 2026) names TableCheck Inc., KR Ginza II 5F, 2-15-2 Ginza, Chuo-ku, Tokyo. The API documentation is hosted on tablecheck.atlassian.net. api.tablecheck.com redirects there. www.tablecheck.com/.well-known/security.txt returns an HTML page, read as no security.txt. RDAP gives a registration date of 1998-07-01 for tablecheck.com. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://tablecheck.atlassian.net/wiki/spaces/API/pages/61571353/TableCheck+API+Terms+of+Service), read 2026-10-14, dated 2022-10-11, states 6 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "…monitor the availability, performance, or functionality of any of the API or Services or for any similar benchmarking purposes." - To know. Says access can be ended without notice or for any reason. "We may terminate the Agreement with or without cause and without notice to you." - To know. Has not been updated for three years or more. "Updated 2022-10-11" - Gives the date it was last updated. Last updated 2022-10-11. - Names the governing law or courts. Disputes go to the courts of Beijing. - Says how changes to the terms are announced. Says it gives notice of a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-14). Liability for all claims under the agreement is capped at 100 US dollars. "IN NO EVENT WILL OUR AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THE AGREEMENT (WHETHER IN CONTRACT OR TORT OR UNDER ANY OTHER THEORY OF LIABILITY) EXCEED ONE HUNDRED U.S. DOLLARS ($100.00)." - Also in the text (2026-10-14). The developer grants TableCheck a licence to use its company name and logo in marketing and promotional communications. "You grant us a non-exclusive, royalty-free, fully paid-up, worldwide right and license to use your company name and logo as a reference for marketing or promotional purposes on our website and in other public or private communications with our existing or potential developers and customers" **Privacy policy** (https://www.tablecheck.com/en/policy/privacy), read 2026-10-14, dated 2016-12-14, states 7 of the 8 things a reader expects. - To know. Has not been updated for three years or more. "Revised on December 14, 2016" - Gives the date it was last updated. Last updated 2016-12-14. - Not found in the text. Says what rights people have over their data. - Gives a privacy contact. Names a data protection officer. - Also in the text (2026-10-14). TableCheck may calculate Customer Scores reflecting a diner's reliability from reservation, cancellation, visit and payment history. "We may also analyze reservation history, cancellation history, visit history, payment information, survey responses, account usage status, and other information held by us to calculate indicators, scores, or ranks that reflect a user’s reliability" ## Live (updated 2026-10-14 09:42 UTC) - Right now: up, HTTP 200, 717 ms, checked 2026-10-14 09:42 UTC (get on `https://api.tablecheck.com/api/`) - Uptime 24h 100.0% (17 probes) · 30 days 100.0% (17 probes) · p50 711 ms · p95 871 ms - Vendor status page: none, All Systems Operational - Always current: https://www.anchorterminal.com/api/v1/live/tablecheck.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - OpenAPI 3.0 YAML served for each component, with a written change and deprecation policy - Separate APIs for diner-side platforms (Availability, Distribution, Web Booking) and venue-side systems (Booking, CRM, POS) - MCP for Merchants hides guest names, phones and emails unless asked and supports read-only keys - MCP write tools take an idempotency key and are annotated destructive - Rate limit stated as 10,000 requests per 5 minutes per component ## Weaknesses - Access needs an emailed application, case-by-case approval and fees quoted privately - MCP for Merchants is under development and its tools may change without a version bump - REST POST /reservations has no idempotency key - Keys are issued and rolled only by the API team, with no audit log found - Booking v1 needs per-venue approval for aggregators, and only a production environment exists by default ## Before you call it (notes for agents) 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 Claude Code: ```bash claude mcp add --transport http tablecheck \ https://api.staging-qa.tablecheck.com/api/mcp_merchant/v1 \ --header "Authorization: Bearer $TABLECHECK_API_KEY" ``` MCP client configuration: ```json { "mcpServers": { "tablecheck": { "headers": { "Authorization": "Bearer ${TABLECHECK_API_KEY}" }, "type": "http", "url": "https://api.staging-qa.tablecheck.com/api/mcp_merchant/v1" } } } ``` Through letme (picks today, calling later): https://letme.dev/tablecheck (letme picks it for booking.orders, the top-graded tool for the job, letme picks it for booking.reservations, the top-graded tool for the job). letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Eat App Partner API | D | 53.4 | 752 | booking.reservations, booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/eat-app.md | | TheFork B2B API | E | 43.6 | 951 | booking.reservations, booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/thefork.md | | OpenTable APIs | E | 38.6 | 994 | booking.availability, booking.reservations, booking.venue | no | https://www.anchorterminal.com/tools/opentable.md | | SevenRooms | F | 17.7 | 1043 | booking.venue, booking.reservations, booking.availability | no | https://www.anchorterminal.com/tools/sevenrooms.md | | Resy | F | 10.3 | 1068 | booking.reservations, booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/resy.md | | Square Appointments (Bookings API) | B | 68.1 | 242 | booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/square-appointments.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - MCP for Merchants v1 is "Under Development", and TableCheck asks users not to build unattended integrations against it (source: ) - The MCP server exposes 20 tools across availability, booking, CRM and POS, from `check_availability` and `hold_table` to `cancel_reservation` and `set_table_status` (source: ) - Three booking APIs, Distribution v1 and Web Booking v1 for listing and travel sites and Booking v1 for merchant-owned sites (source: ) - A REST blockage locks a table for 5 minutes before POST /reservations and can be renewed (source: ) - Rate limit of 10,000 requests per 5 minutes per component, with a hard cutoff (source: ) - Old api.tablesolution.com URLs returned 308 from 3 June 2026 and were to be shut off by 2 October 2026 (source: ) - #2 of 9 in 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 ## Compare - [Chope vs TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.md): F 13.3 vs C 57.1 - [Eat App Partner API vs TableCheck API](https://www.anchorterminal.com/compare/eat-app-vs-tablecheck.md): D 53.4 vs C 57.1 - [Resy vs TableCheck API](https://www.anchorterminal.com/compare/resy-vs-tablecheck.md): F 10.3 vs C 57.1 - [TableCheck API vs Tock](https://www.anchorterminal.com/compare/tablecheck-vs-tock.md): C 57.1 vs F 12.4 - [OpenTable APIs vs TableCheck API](https://www.anchorterminal.com/compare/opentable-vs-tablecheck.md): E 38.6 vs C 57.1 - [Square Appointments (Bookings API) vs TableCheck API](https://www.anchorterminal.com/compare/square-appointments-vs-tablecheck.md): B 68.1 vs C 57.1 - [TableCheck API vs TheFork B2B API](https://www.anchorterminal.com/compare/tablecheck-vs-thefork.md): C 57.1 vs E 43.6 - [SevenRooms vs TableCheck API](https://www.anchorterminal.com/compare/sevenrooms-vs-tablecheck.md): F 17.7 vs C 57.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on tablecheck.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "tablecheck", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html TableCheck API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![TableCheck API on Anchor Terminal](https://www.anchorterminal.com/badges/tablecheck.svg)](https://www.anchorterminal.com/tools/tablecheck) ``` Plain link: ```html TableCheck API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say TableCheck API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/tablecheck-dark.png - Light: https://www.anchorterminal.com/assets/share/tablecheck-light.png - Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=tablecheck