# Reclaim.ai vs Zoom Scheduler API (slim)

> Zoom Scheduler scores 51.9 (D) 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/reclaim-ai-vs-zoom-scheduler.md (~4,350 tokens) · this version ~2,330 tokens · JSON https://www.anchorterminal.com/compare/reclaim-ai-vs-zoom-scheduler.json · canonical https://www.anchorterminal.com/compare/reclaim-ai-vs-zoom-scheduler
- 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)

Zoom Scheduler API scores 51.9 (D) on agent readiness against Reclaim.ai's 37.9 (F), and leads in 6 of 7 scored categories. Both do calendar access.

- Reclaim.ai: F 37.9, rank #1349 of 1486 · https://www.anchorterminal.com/tools/reclaim-ai.min.md
- Zoom Scheduler API: D 51.9, rank #1003 of 1486 · https://www.anchorterminal.com/tools/zoom-scheduler.min.md
- Reclaim.ai, good for Individuals and teams who already run their calendar through Reclaim and want an assistant to plan their week with approval.
- Zoom Scheduler API, good for An agent booking into a Zoom Scheduler user's or team's booking pages, with slot lookup, booking, cancellation and three webhooks. Ahead on Reliability, 65 against 45; Schema & documentation, 61 against 28; Agent ergonomics, 43 against 30; Maintenance & community, 38 against 25; Transparency & trust, 70 against 56.

| Category | Reclaim.ai | Zoom Scheduler API |
| --- | --- | --- |
| Reliability (16%) | 45 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 28 | 61 |
| Agent ergonomics (13%) | 30 | 43 |
| Security & auth (14%) | 53 | 54 |
| Payments & pricing (10%) | 25 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 25 | 38 |
| Transparency & trust (7%) | 56 | 70 |

| Fact (where they differ) | Reclaim.ai | Zoom Scheduler API |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Reclaim.ai Inc. | Zoom Communications, Inc. |
| Hosted endpoint | `https://mcp.reclaim.ai` | `https://api.zoom.us/v2` |
| Transports | Streamable HTTP | HTTP |
| Pricing | Freemium | Paid |
| Licence | none | Proprietary service under the Zoom API Licence and Terms of Use |
| llms.txt | no | yes |
| Last release | none | 2026-10-19 |
| Terms last updated | 2024-04-08 | 2025-07-16 |
| Privacy policy last updated | 2025-06-25 | 2026-09-17 |
| Terms restrict benchmarking | not found in the text | yes |

Why the edge:
- Schema & documentation, Zoom Scheduler API +33: 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.); Zoom Scheduler API 61 (The reference states OpenAPI version 3.1.1, but no specification file is linked from the page, the API catalogue or llms.txt. A Markdown copy of the whole reference is published (10). Markdown copies of pages and an API catalogue at `/.well-known/api-catalog.json`. The llms.txt that every docs page links answered 404 on 4 November 2026, so the line rests on the Markdown copies (10). Most operations carry one line such as "Patches a scheduled event". The available times and booking operations say when to use them (8). Request bodies are typed, with 55 required marks, 38 enumerated fields and email, date and date-time formats. The Markdown copy and the static page omit query and path parameters (9). Every request body has an example and each operation lists its error statuses with a code name, some misspelt (11). The path is versioned v2 and the changelog has dated Scheduler entries (13). Total 61.)
- Reliability, Zoom Scheduler API +20: 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.); Zoom Scheduler API 65 (Graded as a hosted API. Statuspage site at status.zoom.us (redirects to www.zoomstatus.com) with Zoom Scheduler as its own component and REST API and Webhooks under Zoom Developer Platform, per the 9 October check (20). The Atom feed read on 4 November holds 25 entries from 19 October to 4 November 2026, none naming Scheduler or the REST API. The 23 October degradation of "multiple Zoom Services" (09:01 to 09:48 PDT, an external vendor) names no product. The window from 6 August to 18 October could not be read, because the history page is drawn by script and robots.txt closes /api/, so the line keeps its recorded 10. Every Scheduler operation is labelled Light, which is 4 a second and 6,000 a day on Free, 30 a second on Pro and 80 a second on Business and above, per account (15). The rate-limit page says to handle 429 by waiting before retrying and to build retry mechanisms, and the daily-limit message points to a response header for when to resume. No idempotency key or safe-retry guidance exists for booking writes, so the settled value for backoff guidance alone applies (10). No SLA found, and the API terms say Zoom does not guarantee uptime (0). No beta label on the Scheduler API, and Zoom's lifecycle page treats an initial release as stable (10). 20 + 10 + 15 + 10 + 0 + 10 = 65.)
- Transparency & trust, Zoom Scheduler API +14: Reclaim.ai 56 (Closed service under terms of 8 April 2024 naming Reclaim.ai Inc. (15 of 30). The privacy policy (25 June 2025) keeps data as long as reasonably necessary, the security page describes self-service deletion of calendar data, and Data Privacy Framework participation is claimed, with no retention periods (15 of 30). Reclaim 1.0 users are moved to 2.0, and no deprecation policy or dates were found (3 of 20). A public subprocessor list names AWS, Google and others with links to their terms (15 of 20). 15 + 15 + 3 + 15 = 48.); Zoom Scheduler API 70 (Closed service under the Zoom API Licence and Terms of Use of 16 July 2025 (15). The Privacy Statement of 17 September 2026 gives no fixed retention periods. The Terms of Service delete customer content 30 days after termination, and both documents say communications-like customer content is not used to train AI models. The DPA is a PDF we did not read (18). A lifecycle page describes deprecation and sunset stages and the changelog tags them, but the API terms let Zoom change or deprecate APIs without prior notice, with only commercially reasonable efforts to tell developers (8). The sub-processor list, updated 2 October 2026, names 24 third parties and 23 affiliates with locations and has an email sign-up for changes (18). Total 59.)
- Agent ergonomics, Zoom Scheduler API +13: 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.); Zoom Scheduler API 43 (No field selection was found, and a schedule object runs to several hundred lines of fields. Query parameters could not be read (8). List responses return `next_page_token`, and the changelog records filters by team, account scope and created or updated time. The parameter list itself was not readable (14). Errors carry a status and a short code name such as InvalidArgument, NotFound or Conflict, with a 409 on booking conflicts and little detail (12). No idempotency key or safe-retry guidance for `POST /scheduler/attendee` (3). Booking needs six fields. No official SDK covers Scheduler, and Zoom Rivet 0.3.0 has no Scheduler module (6). Total 43.)
- Maintenance & community, Zoom Scheduler API +13: 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.); Zoom Scheduler API 38 (The latest Scheduler changelog entry is 19 October 2026, an API release adding the `scheduler.routing_form_submission_created` webhook, 16 days before this check (30). Two dated entries in the 90 days from 6 August, 17 August and 19 October (0). A public changelog with a developer forum thread for each entry and a developer support page. Whether the forum answers was not checked (8). No official SDK covers Scheduler, and Zoom Rivet 0.3.0 still has no Scheduler module (0). No package to assess (0). 30 + 0 + 8 + 0 + 0 = 38.)