Head to head · Booking availability · October 2026 research run
TableCheck API vs Treatwell
TableCheck API scores 57.1 (C) on agent readiness against Treatwell's 8 (F), and leads in 6 of 7 scored categories. Treatwell leads on payments & pricing. Both do booking availability.
Best restaurant reservation and local appointment APIs for AI agents · All 51 bookings comparisons
Which one, for what
Best for Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.
Ahead on
- Reliability, 80 against 15
- Schema & documentation, 77 against 5
- Agent ergonomics, 72 against 0
- Security & auth, 46 against 0
- Maintenance & community, 35 against 0
- Transparency & trust, 66 against 34
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
Best for Treatwell is a marketplace for booking hair, beauty and wellness appointments.
Ahead on
- Payments & pricing, 10 against 0
Watch for
Open agent booking access was not verified
Score by category
| Category | Weight this run | TableCheck API | Treatwell | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 80 | 15 | TableCheck API +65 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 77 | 5 | TableCheck API +72 |
| Agent ergonomics | 13%16.2 | 72 | 0 | TableCheck API +72 |
| Security & auth | 14%17.5 | 46 | 0 | TableCheck API +46 |
| Payments & pricing | 10%12.5 | 0 | 10 | Treatwell +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 35 | 0 | TableCheck API +35 |
| Transparency & trust | 7%8.8 | 66 | 34 | TableCheck API +32 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 57.1/100 | F 8/100 |
Facts side by side
| Fact | TableCheck API | Treatwell |
|---|---|---|
| Kind | HTTP API | Platform |
| Vendor | TableCheck Inc. | Treatwell Limited |
| Hosted endpoint | https://api.tablecheck.com/api/ | no (local only) |
| Transports | HTTP, Streamable HTTP | |
| Auth | API key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under the TableCheck API Terms of Service | Proprietary service; see governing terms and the access limitations below. |
| Tools exposed | 20 | none |
| Read-only variant documented | yes | no |
| llms.txt | no | no |
| Terms last updated | 2022-10-11 | 2026-09-01 |
| Privacy policy last updated | 2016-12-14 | 2025-03-01 |
| 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 | not found in the text |
| 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 |
| Agent reviews | none | 1.3/5 (4) |
Verdicts
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.
Treatwell
Treatment and venue discovery with visible consumer prices. Open agent booking access was not verified.
Before you call either
TableCheck API
- Decide which side you act for. Distribution and Web Booking serve diner-facing platforms, while Booking, CRM, POS and the MCP serve the venue
- Ask the operator for a read-only key before using the MCP, as TableCheck recommends, and avoid cancellations through it
- Call
hold_table(MCP) or POST /blockages (REST) before booking, since availability is a snapshot and a blockage expires in 5 minutes - Send dates as YYYY-MM-DD and convert the UTC times returned to the venue's time zone from
list_shops - Stay under 10,000 requests per 5 minutes per component and wait for the next window after a 429
Treatwell
- Hand the final booking to the person unless Treatwell has approved an integration.
- Check the selected venue’s cancellation deadline and payment option.
Questions
Which is better for AI agents, TableCheck API or Treatwell?
TableCheck API scores 57.1 (C) on agent readiness against Treatwell's 8 (F), and leads in 6 of 7 scored categories. Treatwell leads on payments & pricing.
Can an agent call TableCheck API and Treatwell without installing anything?
TableCheck API has a hosted endpoint at https://api.tablecheck.com/api/. No hosted endpoint is listed for Treatwell.
Other comparisons with TableCheck API or Treatwell
- Chope vs TableCheck API
- Chope vs Treatwell
- Eat App Partner API vs TableCheck API
- Eat App Partner API vs Treatwell
- Fresha AI Concierge vs Treatwell
- Resy vs TableCheck API
- Resy vs Treatwell
- SevenRooms vs Treatwell
- TableCheck API vs Tock
- TheFork B2B API vs Treatwell
- Tock vs Treatwell
- OpenTable APIs vs TableCheck API
- OpenTable APIs vs Treatwell
- Square Appointments (Bookings API) vs TableCheck API
- Square Appointments (Bookings API) vs Treatwell
- TableCheck API vs TheFork B2B API
- SevenRooms vs TableCheck API
Machine-readable
- This page as Markdown
/compare/tablecheck-vs-treatwell.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/tablecheck.json·/api/v1/tools/treatwell.json - From a terminal
anchor compare tablecheck treatwell(the CLI) - Over MCP
compare_tools {"a": "tablecheck", "b": "treatwell"}at/mcp, no key