Head to head · Booking availability · October 2026 research run
Square Appointments (Bookings API) vs TableCheck API
Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against TableCheck API's 57.1 (C), and leads in 6 of 7 scored categories. TableCheck API leads on reliability. Both do booking availability.
Best restaurant reservation and local appointment APIs for AI agents · All 36 bookings comparisons
Which one, for what
Square Appointments (Bookings API) B
Best for Venue-side appointment booking for salons, clinics and other service businesses already on Square.
Ahead on
- Schema & documentation, 89 against 77
- Agent ergonomics, 80 against 72
- Security & auth, 70 against 46
- Payments & pricing, 40 against 0
- Maintenance & community, 71 against 35
Also in its favour
- Runs on your own machine
Watch for
Seller-level create, update and cancel fail with 403 unless the seller pays for Plus ($49) or Premium ($149) per location
Best for Restaurants and groups in Japan and Asia on TableCheck, and booking or concierge platforms wanting their inventory.
Ahead on
- Reliability, 80 against 55
Watch for
Access needs an emailed application, case-by-case approval and fees quoted privately
Score by category
| Category | Weight this run | Square Appointments (Bookings API) | TableCheck API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 55 | 80 | TableCheck API +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 77 | Square Appointments (Bookings API) +12 |
| Agent ergonomics | 13%16.2 | 80 | 72 | Square Appointments (Bookings API) +8 |
| Security & auth | 14%17.5 | 70 | 46 | Square Appointments (Bookings API) +24 |
| Payments & pricing | 10%12.5 | 40 | 0 | Square Appointments (Bookings API) +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 71 | 35 | Square Appointments (Bookings API) +36 |
| Transparency & trust | 7%8.8 | 70 | 66 | Square Appointments (Bookings API) +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | C 57.1/100 |
Facts side by side
| Fact | Square Appointments (Bookings API) | TableCheck API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Block, Inc. | TableCheck Inc. |
| Hosted endpoint | https://connect.squareup.com/v2/bookings | https://api.tablecheck.com/api/ |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service under the Square Developer Terms of Service. The OpenAPI specification and MCP server are Apache 2.0 | Proprietary service under the TableCheck API Terms of Service |
| Tools exposed | 3 | 20 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-09-16 | none |
| Terms last updated | 2026-09-10 | 2022-10-11 |
| Privacy policy last updated | 2026-09-15 | 2016-12-14 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | 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 | yes | not found in the text |
Verdicts
Square Appointments (Bookings API)
The Bookings API lets an agent working for a Square seller search availability and create, change and cancel appointments, with a public OpenAPI spec, appointment OAuth scopes and idempotency keys. It acts for the venue. Seller-level writes need Plus or Premium, services with a no-show fee can't be booked through it, and it hasn't changed since September 2024.
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
Square Appointments (Bookings API)
- Act for the seller. This API books into one Square seller's calendar, not across businesses
- Call RetrieveBusinessBookingProfile and check
support_seller_level_writesbefore trying to create or cancel a seller-level booking - Call SearchAvailability first, then CreateBooking with the service variation ID and version, team member, location and customer
- Send a fresh
idempotency_keyon each create, update or cancel, and passbooking_versionwhen cancelling - Check
no_show_feeon the service. A service with a non-zero fee must be booked by the customer elsewhere
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
Questions
Which is better for AI agents, Square Appointments (Bookings API) or TableCheck API?
Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against TableCheck API's 57.1 (C), and leads in 6 of 7 scored categories. TableCheck API leads on reliability.
Do Square Appointments (Bookings API) and TableCheck API need an API key?
Square Appointments (Bookings API) takes an API key or an OAuth sign-in. TableCheck API needs an API key.
Can an agent call Square Appointments (Bookings API) and TableCheck API without installing anything?
Yes. Square Appointments (Bookings API) has a hosted endpoint at https://connect.squareup.com/v2/bookings and TableCheck API at https://api.tablecheck.com/api/.
Other comparisons with Square Appointments (Bookings API) or TableCheck API
- Chope vs TableCheck API
- Eat App Partner API vs TableCheck API
- Resy vs TableCheck API
- TableCheck API vs Tock
- Chope vs Square Appointments (Bookings API)
- Eat App Partner API vs Square Appointments (Bookings API)
- OpenTable APIs vs Square Appointments (Bookings API)
- OpenTable APIs vs TableCheck API
- Resy vs Square Appointments (Bookings API)
- Square Appointments (Bookings API) vs TheFork B2B API
- TableCheck API vs TheFork B2B API
- SevenRooms vs Square Appointments (Bookings API)
- SevenRooms vs TableCheck API
- Square Appointments (Bookings API) vs Tock
Machine-readable
- This page as Markdown
/compare/square-appointments-vs-tablecheck.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/square-appointments.json·/api/v1/tools/tablecheck.json - From a terminal
anchor compare square-appointments tablecheck(the CLI) - Over MCP
compare_tools {"a": "square-appointments", "b": "tablecheck"}at/mcp, no key