# Apiroc Unified Calendar API vs Truto Unified Calendar API (slim)

> Truto Unified Calendar scores 60.4 (C) to Apiroc Unified Calendar's 41.2 (E) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/apiroc-vs-truto-calendar.md (~4,650 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/apiroc-vs-truto-calendar.json · canonical https://www.anchorterminal.com/compare/apiroc-vs-truto-calendar
- 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 Apiroc Unified Calendar API's 41.2 (E), and leads in 5 of 7 scored categories. Apiroc Unified Calendar API leads on payments & pricing and maintenance & community. Both do calendar access.

- Apiroc Unified Calendar API: E 41.2, rank #1305 of 1510 · https://www.anchorterminal.com/tools/apiroc.min.md
- Truto Unified Calendar API: C 60.4, rank #655 of 1510 · https://www.anchorterminal.com/tools/truto-calendar.min.md
- Apiroc Unified Calendar API, good for A small product or an agent builder that needs read and write across Google, Microsoft and iCloud for tens to hundreds of accounts on a tight budget. Ahead on Payments & pricing, 40 against 20; Maintenance & community, 62 against 50. Also A hosted endpoint, with nothing to install; Free to start without a card.
- 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 35; Schema & documentation, 75 against 44; Agent ergonomics, 71 against 52; Security & auth, 52 against 21; Transparency & trust, 61 against 51.

| Category | Apiroc Unified Calendar API | Truto Unified Calendar API |
| --- | --- | --- |
| Reliability (16%) | 35 | 77 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 44 | 75 |
| Agent ergonomics (13%) | 52 | 71 |
| Security & auth (14%) | 21 | 52 |
| Payments & pricing (10%) | 40 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 62 | 50 |
| Transparency & trust (7%) | 51 | 61 |

| Fact (where they differ) | Apiroc Unified Calendar API | Truto Unified Calendar API |
| --- | --- | --- |
| Vendor | Apiroc | Yin Yang Inc. |
| Hosted endpoint | `https://api.apiroc.com/api/v1` | no (local only) |
| Transports | HTTP |  |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| Licence | MIT (Node SDK) | none |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-08-05 | 2026-10-26 |
| Terms last updated | 2026-08-24 | no date given |
| Privacy policy last updated | 2026-08-24 | 2024-10-19 |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 26 npm/wk | none |
| Agent reviews | 2/5 (2) | none |

Why the edge:
- Reliability, Truto Unified Calendar API +42: Apiroc Unified Calendar API 35 (No public status page with history. status.apiroc.com doesn't resolve and the homepage shows only an "All systems operational" badge with a claim of 34B+ API calls (0). No readable incident history (5). Rate limits published with numbers, 20 requests a second in Sandbox and 300 in Production per application, plus 600 a minute per Google account and 1,000 a minute per Microsoft account (15). The docs don't mention 429 or Retry-After, though the official Node SDK reads a `retry-after` header on 429, and webhook docs say to dedupe on `svix-id` (5). The terms say availability can't be guaranteed, and no SLA was found on any plan (0). GA, with production use licensed on Pro (10).); 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.)
- Schema & documentation, Truto Unified Calendar API +31: Apiroc Unified Calendar API 44 (No OpenAPI spec. A Postman collection is the only machine-readable contract (10). No llms.txt, per the 30 September check (0). Reference pages for five resources with parameters and cURL, TypeScript and Python examples, but little on when to use one endpoint over another (10). Typed inputs in the Node SDK and required fields marked in the docs (10). Examples throughout, and an errors page that gives only the shape (`error`, `message`, `requestId`) and the 2xx, 4xx and 5xx ranges, with no list of error names (9). `/v1` in the path but no changelog (5).); 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.)
- Security & auth, Truto Unified Calendar API +31: Apiroc Unified Calendar API 21 (Your application calls with one `x-api-key` that reaches every connected end-user account, and we found no key scopes or rotation docs (10). Per-provider scope selection in the dashboard lets an operator request read-only Google or Microsoft scopes, and production requires your own OAuth app. iCloud connects with an app-specific password, which can't be scoped, and nothing asks for confirmation on deletes (8). Event titles and descriptions from third parties reach the caller with no injection guidance (0). Every response carries a `requestId` and the privacy policy keeps application logs 30 days, but we found no operator-facing request log (3). No security.txt (per the 30 September check), no disclosure policy, bounty, SOC 2 or ISO 27001 found (0).); Truto Unified Calendar API 52 (API tokens are per environment and sent as Bearer headers; no scopes or expiry for them were found (20 of 30). Per-account MCP servers can be limited to read methods or tags and set to expire, and the customer's connection form can restrict access to specific resources, but the REST token reaches every integrated account in its environment (14 of 20). Event titles, descriptions and attendee text from outside parties pass through, and no prompt-injection guidance was found (0). Plans keep request logs 30 or 90 days (10 of 15). SOC 2 is stated in a 2023 blog post, with no trust page, security.txt or disclosure policy found (8 of 20). 20 + 14 + 0 + 10 + 8 = 52.)
- Payments & pricing, Apiroc Unified Calendar API +20: Apiroc Unified Calendar API 40 (No x402, MPP or L402 (0). Plan prices and $0.50 per extra end-user account a month published without login (20). Free plan for 10 end-user accounts with no card (20). Browser signup and a dashboard key, no autonomous route (0).); 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.)
- Agent ergonomics, Truto Unified Calendar API +19: Apiroc Unified Calendar API 52 (Lists take `limit` and `pageToken`, and event reads return a `syncToken` for incremental sync (15). Pagination and sync tokens, with free/busy as a separate endpoint (15). Machine-readable `error` names with a `requestId`, but no published list an agent can map to recovery steps (10). No idempotency keys. Events accept a client-supplied `id`, which could make creates safe to retry, though the docs don't say so (5). Node is the only SDK. Python, PHP and Java are listed as on the way (7).); 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.)
- Maintenance & community, Apiroc Unified Calendar API +12: Apiroc Unified Calendar API 62 (Node SDK v2.0.1 on 5 August 2026, 57 days before this check (20). Four SDK releases since 3 July (v1.2.2, v1.3.0, v2.0.0, v2.0.1) (20). No public changelog. Support by email, with priority support on Pro and a Slack channel on Enterprise (4). One current official SDK, in Node (10). CI typechecks, lints, builds and tests on pull requests, and dependencies were bumped in May 2026 (8).); 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.)