# Chope vs Square Appointments (Bookings API)

> Square Appointments scores 68.1 (B) to Chope's 13.3 (F) for booking availability. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/chope-vs-square-appointments
- Markdown: https://www.anchorterminal.com/compare/chope-vs-square-appointments.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/chope-vs-square-appointments.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/chope-vs-square-appointments.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Licence: CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.
- Updated: 2026-10-15

Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Chope's 13.3 (F), and leads in every scored category. Both do booking availability.

- Chope: grade F, 13.3/100, rank #1074 of 1094. Markdown https://www.anchorterminal.com/tools/chope.md · JSON https://www.anchorterminal.com/api/v1/tools/chope.json
- Square Appointments (Bookings API): grade B, 68.1/100, rank #245 of 1094. Markdown https://www.anchorterminal.com/tools/square-appointments.md · JSON https://www.anchorterminal.com/api/v1/tools/square-appointments.json
- Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md
- All 36 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md

## Which one, for what

### Chope (F)

Good for: A person booking restaurants in Singapore, Thailand and Indonesia.

Watch for: No public API or MCP server that an outside agent can call

### Square Appointments (Bookings API) (B)

Good 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 0
- Agent ergonomics, 80 against 0
- Security & auth, 70 against 0
- Payments & pricing, 40 against 30
- Maintenance & community, 71 against 34
- Transparency & trust, 70 against 41

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 | Chope | Square Appointments (Bookings API) | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 15 | 55 | Square Appointments (Bookings API) +40 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 0 | 89 | Square Appointments (Bookings API) +89 |
| Agent ergonomics | 13% (16.2 this run) | 0 | 80 | Square Appointments (Bookings API) +80 |
| Security & auth | 14% (17.5 this run) | 0 | 70 | Square Appointments (Bookings API) +70 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | Square Appointments (Bookings API) +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 34 | 71 | Square Appointments (Bookings API) +37 |
| Transparency & trust | 7% (8.8 this run) | 41 | 70 | Square Appointments (Bookings API) +29 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **13.3 · F** | **68.1 · B** | |

## Facts side by side

| Fact | Chope | Square Appointments (Bookings API) |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | The Chope Group Pte Ltd | Block, Inc. |
| Hosted endpoint | no (local only) | `https://connect.squareup.com/v2/bookings` |
| Transports |  | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Chope's Terms & Conditions | 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 | 2026-09-30 | 2026-09-16 |
| Terms last updated | 2023-09-11 | 2026-09-10 |
| Privacy policy last updated | 2023-09-11 | 2026-09-15 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |

## Verdicts

**Chope.** Chope is a diner-facing restaurant booking site and app in Singapore, Bangkok, Phuket, Jakarta and Bali, owned by Grab, with free bookings and app releases in September 2026. No public API or MCP server lets an outside agent search or book, and restaurant integrations run through partners such as TableCheck and SevenRooms by arrangement.

**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

### Chope

1. Don't plan to call Chope from another agent. Hand the booking to the person, who can use the Chope site, the app or Grab Dine Out
2. For a restaurant on Chope that also uses TableCheck or SevenRooms, check whether that platform's API covers the venue
3. Tell the person that some restaurants ask for a deposit, which depends on the restaurant, day and party size

### Square Appointments (Bookings API)

1. Act for the seller. This API books into one Square seller's calendar, not across businesses
2. Call RetrieveBusinessBookingProfile and check `support_seller_level_writes` before trying to create or cancel a seller-level booking
3. Call SearchAvailability first, then CreateBooking with the service variation ID and version, team member, location and customer
4. Send a fresh `idempotency_key` on each create, update or cancel, and pass `booking_version` when cancelling
5. Check `no_show_fee` on the service. A service with a non-zero fee must be booked by the customer elsewhere

## Questions

### Which is better for AI agents, Chope or Square Appointments (Bookings API)?

Square Appointments (Bookings API) scores 68.1 (B) on agent readiness against Chope's 13.3 (F), and leads in every scored category.

### Can an agent call Chope and Square Appointments (Bookings API) without installing anything?

No hosted endpoint is listed for Chope. Square Appointments (Bookings API) has a hosted endpoint at https://connect.squareup.com/v2/bookings.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/chope-vs-square-appointments.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chope-vs-square-appointments.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "chope", "b": "square-appointments"}`. From a terminal: `anchor compare chope square-appointments`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/chope.json and https://www.anchorterminal.com/api/v1/tools/square-appointments.json

## Other comparisons with Chope or Square Appointments (Bookings API)

- [Chope vs Eat App Partner API](https://www.anchorterminal.com/compare/chope-vs-eat-app.md)
- [Chope vs OpenTable APIs](https://www.anchorterminal.com/compare/chope-vs-opentable.md)
- [Chope vs Resy](https://www.anchorterminal.com/compare/chope-vs-resy.md)
- [Chope vs SevenRooms](https://www.anchorterminal.com/compare/chope-vs-sevenrooms.md)
- [Chope vs TableCheck API](https://www.anchorterminal.com/compare/chope-vs-tablecheck.md)
- [Chope vs TheFork B2B API](https://www.anchorterminal.com/compare/chope-vs-thefork.md)
- [Chope vs Tock](https://www.anchorterminal.com/compare/chope-vs-tock.md)
- [Eat App Partner API vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/eat-app-vs-square-appointments.md)
- [OpenTable APIs vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/opentable-vs-square-appointments.md)
- [Resy vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/resy-vs-square-appointments.md)
- [Square Appointments (Bookings API) vs TableCheck API](https://www.anchorterminal.com/compare/square-appointments-vs-tablecheck.md)
- [Square Appointments (Bookings API) vs TheFork B2B API](https://www.anchorterminal.com/compare/square-appointments-vs-thefork.md)
- [SevenRooms vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/sevenrooms-vs-square-appointments.md)
- [Square Appointments (Bookings API) vs Tock](https://www.anchorterminal.com/compare/square-appointments-vs-tock.md)