# Reclaim.ai vs Truto Unified Calendar API (slim)

> Truto Unified Calendar scores 60.4 (C) 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-truto-calendar.md (~4,250 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/reclaim-ai-vs-truto-calendar.json · canonical https://www.anchorterminal.com/compare/reclaim-ai-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 Reclaim.ai's 37.9 (F), and leads in 5 of 7 scored categories. Reclaim.ai leads on payments & pricing. Both do calendar access.

- Reclaim.ai: F 37.9, rank #1349 of 1486 · https://www.anchorterminal.com/tools/reclaim-ai.min.md
- Truto Unified Calendar API: C 60.4, rank #652 of 1486 · https://www.anchorterminal.com/tools/truto-calendar.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. Ahead on Payments & pricing, 25 against 20. Also A hosted endpoint, with nothing to install.
- 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 45; Schema & documentation, 75 against 28; Agent ergonomics, 71 against 30; Maintenance & community, 50 against 25; Transparency & trust, 61 against 56.

| Category | Reclaim.ai | Truto Unified Calendar API |
| --- | --- | --- |
| Reliability (16%) | 45 | 77 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 28 | 75 |
| Agent ergonomics (13%) | 30 | 71 |
| Security & auth (14%) | 53 | 52 |
| Payments & pricing (10%) | 25 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 25 | 50 |
| Transparency & trust (7%) | 56 | 61 |

| Fact (where they differ) | Reclaim.ai | Truto Unified Calendar API |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Reclaim.ai Inc. | Yin Yang Inc. |
| Hosted endpoint | `https://mcp.reclaim.ai` | no (local only) |
| Transports | Streamable HTTP |  |
| Auth | OAuth | API key |
| Pricing | Freemium | Paid |
| llms.txt | no | yes |
| Last release | none | 2026-10-26 |
| Terms last updated | 2024-04-08 | no date given |
| Privacy policy last updated | 2025-06-25 | 2024-10-19 |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |

Why the edge:
- Schema & documentation, Truto Unified Calendar API +47: 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.); 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.)
- Agent ergonomics, Truto Unified Calendar API +41: 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.); 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.)
- Reliability, Truto Unified Calendar API +32: 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.); 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.)
- Maintenance & community, Truto Unified Calendar API +25: 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.); 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.)
- Payments & pricing, Reclaim.ai +5: 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.); 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.)
- Transparency & trust, Truto Unified Calendar API +5: 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.); 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.)