# Truto Unified Calendar API vs Zoom Scheduler API (slim)

> Truto Unified Calendar scores 60.4 (C) to Zoom Scheduler's 51.9 (D) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/truto-calendar-vs-zoom-scheduler.md (~4,950 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/truto-calendar-vs-zoom-scheduler.json · canonical https://www.anchorterminal.com/compare/truto-calendar-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)

Truto Unified Calendar API scores 60.4 (C) on agent readiness against Zoom Scheduler API's 51.9 (D), and leads in 4 of 7 scored categories. Zoom Scheduler API leads on payments & pricing and transparency & trust. Both do calendar access.

- Truto Unified Calendar API: C 60.4, rank #652 of 1486 · https://www.anchorterminal.com/tools/truto-calendar.min.md
- Zoom Scheduler API: D 51.9, rank #1003 of 1486 · https://www.anchorterminal.com/tools/zoom-scheduler.min.md
- Truto Unified Calendar API, good for Software companies that need their product's agent to read and book across customers' Google, Outlook, Cal.com and Calendly accounts. Ahead on Reliability, 77 against 65; Schema & documentation, 75 against 61; Agent ergonomics, 71 against 43; Maintenance & community, 50 against 38.
- 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 Payments & pricing, 25 against 20; Transparency & trust, 70 against 61. Also A hosted endpoint, with nothing to install.

| Category | Truto Unified Calendar API | Zoom Scheduler API |
| --- | --- | --- |
| Reliability (16%) | 77 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 61 |
| Agent ergonomics (13%) | 71 | 43 |
| Security & auth (14%) | 52 | 54 |
| Payments & pricing (10%) | 20 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 50 | 38 |
| Transparency & trust (7%) | 61 | 70 |

| Fact (where they differ) | Truto Unified Calendar API | Zoom Scheduler API |
| --- | --- | --- |
| Vendor | Yin Yang Inc. | Zoom Communications, Inc. |
| Hosted endpoint | no (local only) | `https://api.zoom.us/v2` |
| Transports |  | HTTP |
| Auth | API key | OAuth |
| Licence | none | Proprietary service under the Zoom API Licence and Terms of Use |
| Last release | 2026-10-26 | 2026-10-19 |
| Terms last updated | no date given | 2025-07-16 |
| Privacy policy last updated | 2024-10-19 | 2026-09-17 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |

Why the edge:
- Agent ergonomics, Truto Unified Calendar API +28: Truto Unified Calendar API 71 (`truto_exclude_fields`, `truto_ignore_remote_data`, `truto_key_by` and response formats (`unified`, `raw`, `normalized`) size the reply (22 of 25). Query operators such as `[gt]` and `[in]`, `sort_by`, `limit` and cursors, with a meta endpoint that says which filters each vendor supports (18 of 20). Errors name the HTTP status and say whether Truto or the provider failed, with the provider's message extracted (18 of 20). No idempotency key found for creates (5 of 20). Every call needs only the token and `integrated_account_id`; a CLI and the Link SDK exist, with no general API SDK found (8 of 15). 22 + 18 + 18 + 5 + 8 = 71.); 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.)
- Schema & documentation, Truto Unified Calendar API +14: Truto Unified Calendar API 75 (An OpenAPI specification is linked from the RFC 9727 API catalogue, but the file timed out and was not read, so it is credited as published and unverified (20 of 25). llms.txt and a Markdown sibling for every page (10). Parameter descriptions say what each does and what it falls back to, such as `end_time` defaulting to the month of `start_time` (15 of 20). Types, required marks and allowed values such as `focus_time` and `out_of_office` (13 of 15). One documented error shape with provider and Truto fields; few request examples on the reference pages read (12 of 15). Deprecated admin endpoints are marked, but no API changelog was found (5 of 15). 20 + 10 + 15 + 13 + 12 + 5 = 75.); 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, Truto Unified Calendar API +12: Truto Unified Calendar API 77 (Graded as a hosted service on the Unified Calendar API. Better Stack status page with components for api.truto.one health, ping and link-token endpoints and the static IP proxy, with incident history (20). The feed lists "APIs and Dashboard are down" on 29 October 2026 and delayed sync jobs and webhooks on 1 November, which counts as one major outage (10). Truto's own limit is 50 requests every 10 seconds per integrated account, in front of each vendor's (15). A vendor 429 comes back with Retry-After and normalised `ratelimit-limit`, `-remaining` and `-reset` headers, with no idempotency guidance for creates (12 of 15). The Enterprise plan lists an SLA guarantee (10). Generally available (10). 20 + 10 + 15 + 12 + 10 + 10 = 77.); 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.)
- Maintenance & community, Truto Unified Calendar API +12: Truto Unified Calendar API 50 (No API changelog, so the last API change can't be dated; the official @truto/truto-link-sdk was published as 1.3.5 on 26 October 2026, which we take as the latest dated release (20 of 30, since it is the connection widget, not the calendar API). Six Link SDK versions since 8 August (10 of 20, for the same reason). Support through Slack on paid plans, with no public tracker (5 of 15). A CLI and the Link SDK are official, with no API client (10 of 15). Package health not checked (5 of 10). 20 + 10 + 5 + 10 + 5 = 50.); 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.)
- Transparency & trust, Zoom Scheduler API +9: Truto Unified Calendar API 61 (Closed service under terms naming Yin Yang Inc. (15 of 30). Truto says it stores no customer data and calls vendors live, logs are kept 30 or 90 days by plan, data is kept 15 days after termination, and a DPA is public (25 of 30). Deprecated admin endpoints are marked with no policy or dates (6 of 20). Enterprise customers can choose a data region and tokens can be stored regionally; no subprocessor list was found (8 of 20). 15 + 25 + 6 + 8 = 54.); 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.)
- Payments & pricing, Zoom Scheduler API +5: Truto Unified Calendar API 20 (No x402, MPP or L402 (0). Plan prices per connector a year are public, with unlimited calls (10). A free 30-day sandbox is given after a work-email request reviewed within a business day (10 of 20). A person requests access or books a demo (0). 0 + 10 + 10 + 0 = 20.); Zoom Scheduler API 25 (No x402, MPP or L402 (0). Seat prices are public, $5.99 a user a month or $4.99 billed yearly, with nothing per call (10). Scheduler Basic is free with no card and a 14-day trial is advertised, but the pricing page lists API access under the paid plan and whether the free plan or the trial can call the API was not established (15). A person signs up and creates a Marketplace app in a browser (0). Total 25.)