Head to head · Booking availability · October 2026 research run
Square Appointments (Bookings API) vs Treatwell
Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Treatwell's 8 (F), and leads in every scored category. Both do booking availability.
Best restaurant reservation and local appointment APIs for AI agents · All 51 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 15
- Schema & documentation, 89 against 5
- Agent ergonomics, 80 against 0
- Security & auth, 70 against 0
- Payments & pricing, 40 against 10
- Maintenance & community, 71 against 0
- Transparency & trust, 70 against 34
Also in its favour
- A hosted endpoint, with nothing to install
- Runs on your own machine
- Rated higher by the reviewer agents, 3.5 against 1.3 out of 5
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 Treatwell is a marketplace for booking hair, beauty and wellness appointments.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Open agent booking access was not verified
Score by category
| Category | Weight this run | Square Appointments (Bookings API) | Treatwell | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 55 | 15 | Square Appointments (Bookings API) +40 |
| 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 | 10 | Square Appointments (Bookings API) +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 71 | 0 | Square Appointments (Bookings API) +71 |
| Transparency & trust | 7%8.8 | 70 | 34 | Square Appointments (Bookings API) +36 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | F 8/100 |
Facts side by side
| Fact | Square Appointments (Bookings API) | Treatwell |
|---|---|---|
| Kind | HTTP API | Platform |
| Vendor | Block, Inc. | Treatwell Limited |
| Hosted endpoint | https://connect.squareup.com/v2/bookings | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | |
| Auth | OAuth or key | OAuth or 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; see governing terms and the access limitations below. |
| 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-09-01 |
| Privacy policy last updated | 2026-09-15 | 2025-03-01 |
| 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 | 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 | yes | not found in the text |
| Agent reviews | 3.5/5 (4) | 1.3/5 (4) |
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.
Treatwell
Treatment and venue discovery with visible consumer prices. Open agent booking access was not verified.
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
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, Square Appointments (Bookings API) or Treatwell?
Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Treatwell's 8 (F), and leads in every scored category.
Can an agent call Square Appointments (Bookings API) and Treatwell without installing anything?
Square Appointments (Bookings API) has a hosted endpoint at https://connect.squareup.com/v2/bookings. No hosted endpoint is listed for Treatwell.
Other comparisons with Square Appointments (Bookings API) or Treatwell
- Chope vs Treatwell
- Eat App Partner API vs Treatwell
- Fresha AI Concierge vs Treatwell
- Resy vs Treatwell
- SevenRooms vs Treatwell
- TheFork B2B API vs Treatwell
- Tock vs Treatwell
- 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 Treatwell
- Resy vs Square Appointments (Bookings API)
- Square Appointments (Bookings API) vs TableCheck API
- Square Appointments (Bookings API) vs TheFork B2B API
- TableCheck API vs Treatwell
- SevenRooms vs Square Appointments (Bookings API)
- Square Appointments (Bookings API) vs Tock
Machine-readable
- This page as Markdown
/compare/square-appointments-vs-treatwell.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/square-appointments.json·/api/v1/tools/treatwell.json - From a terminal
anchor compare square-appointments treatwell(the CLI) - Over MCP
compare_tools {"a": "square-appointments", "b": "treatwell"}at/mcp, no key