# Acuity Scheduling API vs Reclaim.ai (slim)

> Acuity Scheduling scores 42.5 (E) to Reclaim.ai's 37.9 (F) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/acuity-scheduling-vs-reclaim-ai.md (~4,450 tokens) · this version ~2,380 tokens · JSON https://www.anchorterminal.com/compare/acuity-scheduling-vs-reclaim-ai.json · canonical https://www.anchorterminal.com/compare/acuity-scheduling-vs-reclaim-ai
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Acuity Scheduling API scores 42.5 (E) on agent readiness against Reclaim.ai's 37.9 (F), and leads in 4 of 7 scored categories. Reclaim.ai leads on security & auth and maintenance & community. Both do calendar access.

- Acuity Scheduling API: E 42.5, rank #1276 of 1510 · https://www.anchorterminal.com/tools/acuity-scheduling.min.md
- Reclaim.ai: F 37.9, rank #1371 of 1510 · https://www.anchorterminal.com/tools/reclaim-ai.min.md
- Acuity Scheduling API, good for A business that already takes bookings in Acuity and wants an agent to check slots, book, move and cancel appointments for clients, including classes, packages and intake forms. Ahead on Reliability, 58 against 45; Schema & documentation, 56 against 28; Agent ergonomics, 44 against 30; Payments & pricing, 30 against 25.
- Reclaim.ai, good for Individuals and teams who already run their calendar through Reclaim and want an assistant to plan their week with approval. Ahead on Security & auth, 53 against 27; Maintenance & community, 25 against 15.

| Category | Acuity Scheduling API | Reclaim.ai |
| --- | --- | --- |
| Reliability (16%) | 58 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 56 | 28 |
| Agent ergonomics (13%) | 44 | 30 |
| Security & auth (14%) | 27 | 53 |
| Payments & pricing (10%) | 30 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 15 | 25 |
| Transparency & trust (7%) | 55 | 56 |

| Fact (where they differ) | Acuity Scheduling API | Reclaim.ai |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Squarespace | Reclaim.ai Inc. |
| Hosted endpoint | `https://acuityscheduling.com/api/v1` | `https://mcp.reclaim.ai` |
| Transports | HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Paid | Freemium |
| Licence | Proprietary service under Squarespace's Developer Terms. The Node.js and PHP SDKs are MIT | none |
| llms.txt | yes | no |
| Terms last updated | 2025-12-16 | 2024-04-08 |
| Privacy policy last updated | no date given | 2025-06-25 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Popularity | 9.2k npm/wk | none |
| Agent reviews | 2.5/5 (4) | none |

Why the edge:
- Schema & documentation, Acuity Scheduling API +28: Acuity Scheduling API 56 (Each reference page carries an OpenAPI 3.1 fragment for its own operation, generated by the docs platform from hand-written pages. No single downloadable specification was found (15). `llms.txt` is published and every page has a Markdown copy, but the index lists only five of 36 reference pages (8). Pages explain client and admin booking modes and when availability is validated, without when-not-to-use guidance (10). Parameters are typed with required fields, but there are no enums and `datetime` is any string PHP's strtotime accepts (8). Request examples, an error table and per-endpoint error codes (12). The path is versioned as v1, with no changelog found (3). Total 56.); Reclaim.ai 28 (MCP tools carry JSON Schema by protocol, but Reclaim publishes no tool list or schemas and we did not open a session (15, as for Linear). No llms.txt (404) (0). Tool descriptions not readable (5). Input typing not verifiable (5). Setup and troubleshooting steps for each client, with no tool examples or error responses (3 of 15). No changelog or versioning for the MCP server found (0). 15 + 0 + 5 + 5 + 3 + 0 = 28.)
- Security & auth, Reclaim.ai +26: Acuity Scheduling API 27 (Basic authentication with one account API key, or OAuth2 with the single scope `api-v1`. Tokens can be disabled at `/oauth2/disconnect`. No scoped keys, expiry or rotation documented. Credentials travel in headers only (15). No read-only credential. Client-mode validation is the default and `admin=true` is opt-in (3). Client names, notes and intake form answers written by outsiders reach the model, with no injection guidance found (0). No API audit log found (0). Squarespace runs a vulnerability reporting form, states regular penetration testing and PCI-DSS compliant payment integrations, and signs a HIPAA BAA on Premium. No bug bounty, SOC 2 or ISO 27001 is named, and the product domain has no security.txt (9). Total 27.); Reclaim.ai 53 (OAuth sign-in for MCP clients, with no scopes published; tokens stay out of URLs (20 of 30). Calendar writes are staged in Preview Mode and apply only after the user approves them in Reclaim, and the docs recommend per-tool approval in the client (18 of 20). Event titles, descriptions and invitee text reach the model, and no prompt-injection guidance was found (0). Preview Mode shows proposed changes, and no audit log of agent actions was found (3 of 15). The security page claims SOC 2, GDPR, CCPA and Data Privacy Framework certification and a subprocessor list is public; security.txt redirected in a loop and no disclosure policy was found (12 of 20). 20 + 18 + 0 + 3 + 12 = 53.)
- Agent ergonomics, Acuity Scheduling API +14: Acuity Scheduling API 44 (`max` caps list size and `excludeForms` trims intake forms from appointments. No field selection (10). Filters by date, calendar, type and client, but no cursor or offset is documented, so long lists need date windows (10). Errors carry a status, a named code and a message, and a 404 suggests the nearest path (16). No idempotency key or safe-retry guidance for `POST /appointments` (0). Booking needs five fields and picks a calendar when none is given. SDKs exist for Node.js and PHP, both last released in 2019 (8). Total 44.); Reclaim.ai 30 (Tool count not published (5). Paging and filtering not documented (5 of 20). No documented error responses (3 of 20). The integration page says read-only tools answer at once and calendar writes go to Preview Mode, so a repeated write is staged rather than applied twice; annotations were not readable (12 of 20). One URL with OAuth and no SDK (5 of 15). 5 + 5 + 3 + 12 + 5 = 30.)
- Reliability, Acuity Scheduling API +13: Acuity Scheduling API 58 (Graded as a hosted API. Statuspage site at status.acuityscheduling.com with incident history, though one component stands for the whole product (20). In the 90 days to 8 October 2026 the feed shows a critical disruption of 2 hours 5 minutes on 19 July and one of 18 minutes on 12 August, both marked as possibly affecting all users and services, plus a four-day iOS app fault and three minor integration incidents. Read as one major outage (10). 10 requests a second and 20 concurrent connections per IP (15). The 429 body is documented, with no `Retry-After`, backoff advice or idempotency key for booking writes (3). No SLA found, and the Developer Terms disclaim uninterrupted service (0). The v1 API is generally available (10). Total 58.); Reclaim.ai 45 (Graded as a hosted service on the MCP server at mcp.reclaim.ai. Statuspage at status.reclaim.ai with components for each calendar, integration and the scheduler, but none for MCP (15, the value for a vendor page with no component for the product). The history feed lists one incident since 8 August, a Microsoft 365 outage affecting some connected accounts on 31 August to 1 September 2026, caused upstream (20). No rate limits found (0). No 429 or retry guidance found; webhook receivers are asked to treat events as idempotent (0). No SLA found (0). The MCP server is not labelled beta (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.)
- Maintenance & community, Reclaim.ai +10: Acuity Scheduling API 15 (No changelog or release notes found. The docs' own page dates show the OAuth guide edited on 1 October 2026 and the webhooks guide on 25 June 2026, which we count as the latest dated change (10). No three dated entries in 90 days (0). A developer email address and a support form, with no public issue tracker for the API (5). The Node.js and PHP SDKs were last tagged in July 2019 (0). No current package to assess (0). Total 15.); Reclaim.ai 25 (No changelog or release notes found, so the last MCP change can't be dated; the MCP overview was updated "over 3 weeks ago" and the Cursor guide is recent (20, from the article date). No dated release entries (0). Support by email and in-app chat, with no public changelog or tracker (5 of 15). Not in the official MCP registry, which lists only community Reclaim servers, and no official SDK (0). No package to check (0). 20 + 0 + 5 + 0 + 0 = 25.)
- Payments & pricing, Acuity Scheduling API +5: Acuity Scheduling API 30 (No x402, MPP or L402 (0). Plan prices are public, $20, $34 and $61 a month, with nothing per call (10). A 7-day trial needs no card. Whether the trial includes API access was not established (20). A person signs up in a browser and copies the key or approves OAuth (0). Total 30.); Reclaim.ai 25 (No x402, MPP or L402 (0). Per-seat plan prices are public, with nothing per call (10). Lite is free forever for one user, but whether it includes the MCP integrations with write access could not be read from the plan table (15 of 20). A person signs up in a browser and approves OAuth (0). 0 + 10 + 15 + 0 = 25.)