Head to head · Venue management · October 2026 research run
Square Appointments (Bookings API) vs Tock
Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Tock's 12.4 (F), and leads in every scored category. Both do venue management.
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
- Reliability, 55 against 25
- Schema & documentation, 89 against 5
- Agent ergonomics, 80 against 0
- Security & auth, 70 against 0
- Payments & pricing, 40 against 0
- Maintenance & community, 71 against 23
- Transparency & trust, 70 against 52
Also in its favour
- A hosted endpoint, with nothing to install
- 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
Tock F
Best for Restaurants and wineries taking reservations and experience bookings, and for diners booking in person.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No public API or MCP server an outside agent can call. The docs index reads "Docs coming soon"
Score by category
| Category | Weight this run | Square Appointments (Bookings API) | Tock | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 55 | 25 | Square Appointments (Bookings API) +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 5 | Square Appointments (Bookings API) +84 |
| Agent ergonomics | 13%16.2 | 80 | 0 | Square Appointments (Bookings API) +80 |
| Security & auth | 14%17.5 | 70 | 0 | Square Appointments (Bookings API) +70 |
| 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 | 23 | Square Appointments (Bookings API) +48 |
| Transparency & trust | 7%8.8 | 70 | 52 | Square Appointments (Bookings API) +18 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | F 12.4/100 |
Facts side by side
| Fact | Square Appointments (Bookings API) | Tock |
|---|---|---|
| Kind | HTTP API | Platform |
| Vendor | Block, Inc. | Tock (American Express) |
| Hosted endpoint | https://connect.squareup.com/v2/bookings | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | |
| 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 Tock Terms of Use (effective 12 February 2026) and merchant terms |
| Tools exposed | 3 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-09-16 | none |
| Terms last updated | 2026-09-10 | 2026-02-12 |
| Privacy policy last updated | 2026-09-15 | 2025-11-24 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
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.
Tock
Tock takes reservations and experience bookings for restaurants and wineries and now feeds its venues into Resy. There is no public API or MCP server an outside agent can call today. api.exploretock.com publishes reservation data models without endpoints, and the Terms of Use forbid automated access to the site.
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
Tock
- Don't plan to call Tock from another agent. Hand the booking to the person on exploretock.com or in the Resy app
- Do not script the Tock website, which the Terms of Use forbid. A venue wanting data should ask Tock through its dashboard account
Questions
Which is better for AI agents, Square Appointments (Bookings API) or Tock?
Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Tock's 12.4 (F), and leads in every scored category.
Can an agent call Square Appointments (Bookings API) and Tock without installing anything?
Square Appointments (Bookings API) has a hosted endpoint at https://connect.squareup.com/v2/bookings. No hosted endpoint is listed for Tock.
Other comparisons with Square Appointments (Bookings API) or Tock
- Chope vs Tock
- Eat App Partner API vs Tock
- OpenTable APIs vs Tock
- Resy vs Tock
- TableCheck API vs Tock
- TheFork B2B 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)
- Resy vs Square Appointments (Bookings API)
- Square Appointments (Bookings API) vs TableCheck API
- Square Appointments (Bookings API) vs TheFork B2B API
- SevenRooms vs Square Appointments (Bookings API)
- SevenRooms vs Tock
Machine-readable
- This page as Markdown
/compare/square-appointments-vs-tock.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/square-appointments.json·/api/v1/tools/tock.json - From a terminal
anchor compare square-appointments tock(the CLI) - Over MCP
compare_tools {"a": "square-appointments", "b": "tock"}at/mcp, no key