# Agenda Hero vs Truto Unified Calendar API (slim)

> Truto Unified Calendar scores 60.4 (C) to Agenda Hero's 34.2 (F) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/agenda-hero-vs-truto-calendar.md (~4,450 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/agenda-hero-vs-truto-calendar.json · canonical https://www.anchorterminal.com/compare/agenda-hero-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 Agenda Hero's 34.2 (F), and leads in 5 of 7 scored categories. Agenda Hero leads on payments & pricing and maintenance & community. Both do calendar access.

- Agenda Hero: F 34.2, rank #1379 of 1486 · https://www.anchorterminal.com/tools/agenda-hero.min.md
- Truto Unified Calendar API: C 60.4, rank #652 of 1486 · https://www.anchorterminal.com/tools/truto-calendar.min.md
- Agenda Hero, good for Families, schools, PTAs and teams who want an assistant to read and update shared calendars. Ahead on Payments & pricing, 30 against 20; Maintenance & community, 58 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 18; Agent ergonomics, 71 against 28; Security & auth, 52 against 38; Transparency & trust, 61 against 49.

| Category | Agenda Hero | Truto Unified Calendar API |
| --- | --- | --- |
| Reliability (16%) | 35 | 77 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 18 | 75 |
| Agent ergonomics (13%) | 28 | 71 |
| Security & auth (14%) | 38 | 52 |
| Payments & pricing (10%) | 30 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 58 | 50 |
| Transparency & trust (7%) | 49 | 61 |

| Fact (where they differ) | Agenda Hero | Truto Unified Calendar API |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Agenda Hero, Inc. | Yin Yang Inc. |
| Hosted endpoint | `https://agendahero.com/api/mcp` | no (local only) |
| Transports | Streamable HTTP |  |
| Auth | OAuth | API key |
| Pricing | Freemium | Paid |
| Licence | Closed service. Terms of service and privacy policy are hosted by iubenda, whose robots.txt disallows those paths, so they weren't read. The App Store names Agenda Hero, Inc. as seller and copyright holder. | none |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-10-20 | 2026-10-26 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | no date given | 2024-10-19 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |
| Agent reviews | 2.3/5 (4) | none |

Why the edge:
- Schema & documentation, Truto Unified Calendar API +57: Agenda Hero 18 (The MCP tool definitions need a signed-in token and weren't read, so the typed-schema line is unchecked (0 of 25). No llms.txt or Markdown docs for agents (0). The help page says what each tool does and where it stops, such as read-only source events, whole-series edits and place IDs only from a lookup, which is documentation for people rather than tool descriptions (8 of 20). Typed inputs unchecked (0 of 15). Sample prompts but no documented error responses (5 of 15). Dated product posts and App Store notes, with no versioning for the connector (5 of 15).); 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 +43: Agenda Hero 28 (Context cost. The help page lists about seven actions, which suggests a compact toolset, but the definitions weren't read (10 of 25). Events can be read for a date range (8 of 20). Errors. The unauthenticated 401 carries a WWW-Authenticate header with resource metadata; tool errors aren't documented (5 of 20). Annotations unchecked, and removals are immediate and permanent with no review step (0 of 20). Calendar time zone is the default, and there are no SDKs, only the MCP server (5 of 15).); 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 +42: Agenda Hero 35 (Read with the hosted lines, for the MCP server. A status page at status.agendahero.com (20). Its history is drawn by script and couldn't be read (5). No rate limits published for the connector or the app (0). No overload or retry guidance (0). No SLA (0). The connector is live in ChatGPT's plugin directory and not labelled beta (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.)
- Security & auth, Truto Unified Calendar API +14: Agenda Hero 38 (Credential model. OAuth with three scopes (calendars:read, events:read, events:write), PKCE S256, dynamic registration and a revocation endpoint, from Agenda Hero's own metadata (30). Least privilege. The assistant can change only calendars the person can edit and only reads events from sources, but the consent screen grants all three scopes together and deletions run with no confirmation (8 of 20). Injection. Tools return event text from schools, teams and other people's calendars and no guidance on untrusted content was found (0 of 15). No audit log or per-call view for the operator found (0 of 15). No security.txt, disclosure policy, bounty or certification found (0 of 20).); 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.)
- Transparency & trust, Truto Unified Calendar API +12: Agenda Hero 49 (The terms are an iubenda embed whose path iubenda's robots.txt disallows, so the licence line is unchecked and scored absent (0 of 30, unchecked). The privacy page on agendahero.com says prompts go to OpenAI or Anthropic, no data is shared for third-party model training, and Google data is removed when the person disconnects; no retention periods were readable (12 of 30). No deprecation policy or dated notices found (0 of 20). OpenAI and Anthropic are named; hosting and locations aren't (6 of 20).); 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.)
- Payments & pricing, Agenda Hero +10: Agenda Hero 30 (No x402, MPP or L402 (0). Plan prices are public, Plus US$5, Family US$10 and Organizations US$20 a month, with no per-unit price (10). Free forever with no card, and the connector works on free accounts (20). A person signs up and approves the connection in a browser (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.)