Head to head · Booking availability · October 2026 research run
Resy vs Square Appointments (Bookings API)
Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Resy's 10.3 (F), and leads in every scored category. Both do booking availability.
Best restaurant reservation and local appointment APIs for AI agents · All 36 bookings comparisons
Which one, for what
Resy F
Best for Diners booking in person through the app.
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 Amex dining MCP endpoint takes only pre-registered OAuth clients
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 0
- Agent ergonomics, 80 against 0
- Security & auth, 70 against 3
- Payments & pricing, 40 against 0
- Maintenance & community, 71 against 25
- Transparency & trust, 70 against 30
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
Score by category
| Category | Weight this run | Resy | Square Appointments (Bookings API) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 25 | 55 | Square Appointments (Bookings API) +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 0 | 89 | Square Appointments (Bookings API) +89 |
| Agent ergonomics | 13%16.2 | 0 | 80 | Square Appointments (Bookings API) +80 |
| Security & auth | 14%17.5 | 3 | 70 | Square Appointments (Bookings API) +67 |
| Payments & pricing | 10%12.5 | 0 | 40 | Square Appointments (Bookings API) +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 25 | 71 | Square Appointments (Bookings API) +46 |
| Transparency & trust | 7%8.8 | 30 | 70 | Square Appointments (Bookings API) +40 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 10.3/100 | B 68.1/100 |
Facts side by side
| Fact | Resy | Square Appointments (Bookings API) |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | Resy (American Express) | Block, Inc. |
| Hosted endpoint | no (local only) | https://connect.squareup.com/v2/bookings |
| Transports | HTTP, Streamable HTTP, stdio | |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service. Resy Network, Inc. publishes separate privacy and merchant terms for Resy and Tock | Proprietary service under the Square Developer Terms of Service. The OpenAPI specification and MCP server are Apache 2.0 |
| Tools exposed | none | 3 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | none | 2026-09-16 |
| Terms last updated | no document linked | 2026-09-10 |
| Privacy policy last updated | couldn't be read | 2026-09-15 |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | yes | |
| Terms restrict benchmarking | yes | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | yes |
Verdicts
Resy
Resy is a large diner reservation network, now including Tock's venues, with American Express behind it. There is no public API or MCP server an outside agent can call today. An Amex-hosted MCP endpoint exists but accepts only pre-registered clients and has no public documentation, and Resy's own terms and privacy pages could not be read.
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.
Before you call either
Resy
- Don't plan to call Resy from another agent. Hand the booking to the person in the Resy app, or use a client that American Express has approved for its dining MCP
- Do not automate the Resy website or app, since Resy runs a bot-detection programme against automated booking
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
Questions
Which is better for AI agents, Resy or Square Appointments (Bookings API)?
Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Resy's 10.3 (F), and leads in every scored category.
Can an agent call Resy and Square Appointments (Bookings API) without installing anything?
No hosted endpoint is listed for Resy. Square Appointments (Bookings API) has a hosted endpoint at https://connect.squareup.com/v2/bookings.
Other comparisons with Resy or Square Appointments (Bookings API)
- Chope vs Resy
- Eat App Partner API vs Resy
- Resy vs SevenRooms
- Resy vs TableCheck API
- Resy vs TheFork B2B API
- Resy vs Tock
- Chope vs Square Appointments (Bookings API)
- Eat App Partner API vs Square Appointments (Bookings API)
- OpenTable APIs vs Resy
- OpenTable APIs 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)
- Square Appointments (Bookings API) vs Tock
Machine-readable
- This page as Markdown
/compare/resy-vs-square-appointments.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/resy.json·/api/v1/tools/square-appointments.json - From a terminal
anchor compare resy square-appointments(the CLI) - Over MCP
compare_tools {"a": "resy", "b": "square-appointments"}at/mcp, no key