{ "data": { "a": { "slug": "savvycal", "name": "SavvyCal API + MCP", "vendor": "SavvyCal, Inc.", "vendorUrl": "https://savvycal.com", "kind": "http-api", "category": "scheduling", "summary": "SavvyCal's scheduling API lists and books events on scheduling links, reads open time slots and manages links, webhooks and workflows, with a hosted MCP server that lets an assistant book, move and cancel meetings.", "url": "https://www.anchorterminal.com/tools/savvycal", "markdownUrl": "https://www.anchorterminal.com/tools/savvycal.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/savvycal.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/savvycal.json", "dns": "savvycal.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.savvycal.com/v1", "packages": [], "auth": "mixed", "authNotes": "Personal access tokens (`pt_secret_...`) made in Settings \u003e Developers, or OAuth 2 authorisation code apps registered there, both sent as `Authorization: Bearer`. OAuth access tokens last 2 hours with a refresh token, and the spec declares no scopes for either. The MCP server at https://savvycal.com/mcp signs in with OAuth 2.1 (PKCE S256, dynamic client registration, scopes `mcp:read` and `mcp:write`, a revocation endpoint) and needs no key.", "pricing": "freemium", "pricingNotes": "The API, webhooks and the MCP server are on every plan including Free, per the plans page. Free accounts connect calendars, make links and run polls, but people can only book a link on Basic ($12 a user a month, $120 a year) or Premium ($20 a user a month, $200 a year). No self-serve trial, a 30-day money-back guarantee instead, and no card is mentioned for Free. 25 per cent off for students, educators and nonprofits.", "priceSummary": "$12 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI spec at api.savvycal.com/v1/spec or the pricing page (checked 2026-11-03). The spec has no 402 response.", "endpoints": [] }, "toolCount": 63, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.savvycal.com/developers", "llmsTxt": "https://docs.savvycal.com/llms.txt", "openapi": "https://api.savvycal.com/v1/spec", "capabilities": [ "calendar.booking", "calendar.availability", "calendar.read", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "remote-mcp", "oauth", "llms-txt", "openapi", "webhooks", "status-page", "security-txt", "closed-source" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 57, "grade": "C", "agentReady": false, "rank": 815, "ranked": true, "rankOf": 1510, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 40, "payments": 30, "reliability": 70, "schema": 74, "security": 50, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat.", "bestFor": "An agent booking on a person's SavvyCal links or driving their account through the MCP server.", "strengths": [ "OpenAPI 3.0.0 spec at api.savvycal.com/v1/spec, llms.txt and a Markdown twin of every docs page", "Hosted MCP server with OAuth 2.1, PKCE, dynamic client registration and `mcp:read` and `mcp:write` scopes, included on every plan", "Webhooks signed with HMAC-SHA256, retried up to 20 times with exponential backoff, over 16 event types", "Status page with calendar connection components and no notices from June to November 2026", "The MCP docs say the assistant asks for confirmation before cancelling meetings, deleting links or inviting teammates" ], "weaknesses": [ "No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)", "No idempotency keys, Retry-After header or official SDK", "No SOC 2 or ISO 27001 certification and no bug bounty, per the security page", "OAuth apps and personal access tokens carry no scopes, so a REST token reaches everything the user can", "Only one dated product update in the 90 days to 3 November 2026, and no API changelog" ], "agentNotes": [ "Call GET /v1/links/{link_id}/slots with `from` and `until` (at most 31 days apart) and book only a returned slot; POST /v1/links/{link_id}/events refuses other times with 422", "Keep event creation under 10 requests a minute per link, failed attempts included, or expect 429 with no Retry-After", "Page with the `after` and `before` cursors from `metadata` and `limit` up to 100; an invalid filter value resets every filter to its default", "Connect the MCP server with a client that supports dynamic client registration, and request `mcp:read` when the task only reads", "Verify webhooks with HMAC-SHA256 over the raw body against `x-savvycal-signature` and answer 2xx quickly" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57 } ], "editorialScores": { "ergonomics": 53, "maintenance": 40, "payments": 30, "reliability": 70, "schema": 74, "security": 50, "transparency": 57 }, "provenanceScore": 89, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.savvycal.com/v1/me -H \"Authorization: Bearer $SAVVYCAL_TOKEN\"", "claudeCode": "claude mcp add --transport http savvycal https://savvycal.com/mcp", "config": { "mcpServers": { "savvycal": { "url": "https://savvycal.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/calendar.booking", "tool": "https://letme.dev/savvycal" }, "area": "everyday", "unitPrices": [ { "item": "Basic", "unit": "seat-month", "usd": 12, "note": "$120 a user a year billed annually" }, { "item": "Premium", "unit": "seat-month", "usd": 20, "note": "$200 a user a year billed annually" } ], "provenance": { "legalEntity": "SavvyCal, Inc.", "domain": "savvycal.com", "domainRegistered": "2020-08-12", "endpointOnVendorDomain": true, "terms": "https://savvycal.com/terms", "privacy": "https://savvycal.com/privacy", "statusPage": "https://savvycal.instatus.com", "changelog": "https://feedback.savvycal.com/updates", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The terms (last updated 21 January 2026) name SavvyCal, Inc. under Minnesota law with AAA arbitration. They forbid access through automated or non-human means and the use of bots, scrapers or data-extraction tools, and do not mention the API, which the separate developer docs cover. Recorded as a fact; the public pages were read.", "savvycal.com/robots.txt disallows /events/ for every crawler, names ClaudeBot and anthropic-ai among twelve AI crawlers with the same rule, and sets Content-Signal ai-train=no, search=yes, ai-input=yes. docs.savvycal.com allows all with ai-train=yes. Nothing under /events/ was fetched.", "The privacy policy (17 October 2026) names SavvyCal, Inc., US servers, Stripe, OpenAI for advertising measurement, and a DPA with Standard Contractual Clauses. The DPA page is dated 16 January 2023.", "RDAP gives savvycal.com a registration date of 12 August 2020.", "security.txt at savvycal.com/.well-known/security.txt names security@savvycal.com, expires 2 May 2027 and points to savvycal.com/security.", "The status page is savvycal.instatus.com (Instatus), linked from the site footer. The What's New board at feedback.savvycal.com/updates is the product changelog." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/savvycal.json", "live": { "slug": "savvycal", "probe": { "target": "https://api.savvycal.com/v1", "method": "get", "lastAt": "2026-11-07T19:22:30.972976869Z", "lastOk": true, "lastStatus": 404, "lastMs": 310, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 278, "p95ms24h": 374, "samples24h": 238, "samples30d": 710, "days": [ { "date": "2026-11-04", "probes": 87, "ok": 87 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://savvycal.instatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:43.631728638Z" }, "securityTxt": { "url": "https://savvycal.com/.well-known/security.txt", "state": "valid", "expires": "2027-05-06T00:00:00.000Z", "checkedAt": "2026-11-07T16:01:55.011978492Z" }, "llmsTxt": { "url": "https://docs.savvycal.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:52.830685072Z" }, "pages": [ { "url": "https://feedback.savvycal.com/updates", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:09:47.662369284Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f4ec340dc498" }, { "url": "https://savvycal.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:18:59.273922081Z", "changedAt": "2026-11-06T13:40:33.154122355Z", "fingerprint": "7905d7d39194" }, { "url": "https://savvycal.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:19:01.81106698Z", "changedAt": "2026-11-06T13:40:35.74920139Z", "fingerprint": "77116bdb20a1" } ], "mcpTools": { "url": "https://savvycal.com/mcp", "checkedAt": "2026-11-07T01:47:30.334924462Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:47:30.334924462Z" }, "updatedAt": "2026-11-07T19:22:30.972976869Z" } }, "answer": "Truto Unified Calendar API scores 60.4 (C) on agent readiness against SavvyCal API + MCP's 57 (C), and leads in 5 of 7 scored categories. SavvyCal API + MCP leads on payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "truto-calendar", "name": "Truto Unified Calendar API", "vendor": "Yin Yang Inc.", "vendorUrl": "https://truto.one", "kind": "http-api", "category": "scheduling", "summary": "Truto's Unified Calendar API gives one REST interface over Google Calendar, Outlook Calendar, Cal.com and Calendly, with calendars, events, availability, event types, contacts and users. It is part of Truto's unified API platform for software companies.", "url": "https://www.anchorterminal.com/tools/truto-calendar", "markdownUrl": "https://www.anchorterminal.com/tools/truto-calendar.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/truto-calendar.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/truto-calendar.json", "dns": "truto-calendar.grade.anchorterminal.com", "transports": [], "packages": [ { "registry": "npm", "name": "@truto/truto-link-sdk" } ], "auth": "api-key", "authNotes": "A Truto API token, created in app.truto.one under Settings \u003e API Tokens for one environment (development, staging or production), sent as `Authorization: Bearer`. Every request names an `integrated_account_id`, the end customer's connected calendar account, whose OAuth tokens Truto holds. Per-account MCP servers can be limited to read or write methods and tags, and given an expiry.", "pricing": "paid", "pricingNotes": "Expansion from $999 per connector a year and Enterprise from $1,999, each with unlimited connections and API calls, sold through a demo. A free 30-day sandbox is given on request with a work email, usually within one business day.", "priceSummary": "$83.25 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the pricing page or the API catalogue (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://truto.one/docs/api-reference/unified-calendar-api/", "llmsTxt": "https://truto.one/docs/llms.txt", "openapi": "https://api.truto.one/schema/openapi.yml", "capabilities": [ "calendar.read", "calendar.write", "calendar.availability", "calendar.booking", "automation.auth" ], "tags": [ "hosted", "unified-api", "paid", "sales-led", "openapi", "llms-txt", "status-page", "webhooks", "google-calendar", "outlook" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 60.4, "grade": "C", "agentReady": false, "rank": 655, "ranked": true, "rankOf": 1510, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 50, "payments": 20, "reliability": 77, "schema": 75, "security": 52, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Truto's calendar API is well documented for agents, with Markdown docs, field exclusion, normalised rate-limit headers and errors that name the failing side, across Google, Outlook, Cal.com and Calendly. It is sold from $999 a connector a year through a demo, had an API outage on 29 October 2026 and has no public changelog.", "bestFor": "Software companies that need their product's agent to read and book across customers' Google, Outlook, Cal.com and Calendly accounts.", "strengths": [ "One REST shape for Google Calendar, Outlook Calendar, Cal.com and Calendly, including availability and event types", "Markdown copy of every docs page and an llms.txt index", "`truto_exclude_fields`, `truto_ignore_remote_data` and response formats to size replies", "Errors say whether Truto or the provider failed, and vendor rate limits come back as standard headers", "Pass-through design with no stored customer data, and a public DPA" ], "weaknesses": [ "Priced from $999 per connector a year with a demo-led sandbox", "An outage of the APIs and dashboard on 29 October 2026 is on the status page", "No public changelog for the API", "API tokens are per environment with no scopes found", "Only five calendar integrations, and Calendly support is partial on events" ], "agentNotes": [ "Pass `integrated_account_id` on every call; the token alone reaches nothing", "Call the meta endpoint for the method first to see which filters the vendor supports", "Set `truto_ignore_remote_data=true` and list fields in `truto_exclude_fields` to keep responses small", "On 429 wait for Retry-After; stay under 50 requests every 10 seconds per integrated account", "Set `expand_recurring=true` when the task needs each instance of a repeating event" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.4 } ], "editorialScores": { "ergonomics": 71, "maintenance": 50, "payments": 20, "reliability": 77, "schema": 75, "security": 52, "transparency": 54 }, "provenanceScore": 67, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.truto.one/unified/calendar/events?integrated_account_id=$ACCOUNT_ID\" -H \"Authorization: Bearer $TRUTO_API_TOKEN\"" }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/truto-calendar" }, "area": "everyday", "unitPrices": [ { "item": "Expansion plan connector", "unit": "month", "usd": 83.25, "note": "From $999 per connector a year" }, { "item": "Enterprise plan connector", "unit": "month", "usd": 166.58, "note": "From $1,999 per connector a year" } ], "provenance": { "legalEntity": "Yin Yang Inc.", "domain": "truto.one", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://truto.one/tos/", "privacy": "https://truto.one/privacy/", "statusPage": "https://status.truto.one", "changelog": "", "securityTxt": "unknown", "checked": "2026-11-06", "notes": [ "truto.one/robots.txt allows all and points to llms.txt, an RFC 9727 API catalogue and agent skills; every page has a Markdown sibling. api.truto.one/robots.txt returned 404. status.truto.one's robots.txt returned no rules.", "The terms name Yin Yang Inc. No clause on automated access was found in the parts read.", "The OpenAPI file at api.truto.one/schema/openapi.yml timed out after 30 seconds and was not read.", "security.txt was not checked. SOC 2 compliance is stated only in a blog post of 24 August 2023; no trust page was found." ], "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/truto-calendar.json", "live": { "slug": "truto-calendar", "vendorStatus": { "page": "https://status.truto.one", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:53.753341884Z" }, "versions": [ { "registry": "npm", "name": "@truto/truto-link-sdk", "version": "1.3.5", "seenAt": "2026-11-07T00:12:59.774757597Z" } ], "npmWeekly": 6850, "securityTxt": { "url": "https://truto.one/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:30.982914489Z" }, "llmsTxt": { "url": "https://truto.one/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:12.104383057Z" }, "pages": [ { "url": "https://truto.one/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:22:35.56420207Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "83d604dc7090" }, { "url": "https://truto.one/tos/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:22:37.675377248Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "fa7045806b26" } ], "updatedAt": "2026-11-07T15:59:30.982914489Z" } }, "edges": [ { "by": 18, "category": "ergonomics", "leads": "truto-calendar", "name": "Agent ergonomics", "reasons": { "a": "List responses are sized by `limit` (default 20, at most 100) with no field selection. The MCP server lists 63 tools with no documented toolset or read-only list, though a client can ask for the `mcp:read` scope alone (10 of 25). Cursor pagination with `after`, `before` and `limit`, and date and status filters on events (17 of 20). Errors name the field, the failed validation and a limit count, which an agent can act on, but a 429 carries no wait time (14 of 20). No idempotency key on booking or link creation, and the MCP annotations could not be read; the docs say the assistant confirms before cancelling, deleting or inviting (6 of 20). Creating an event needs five fields, and there is no official SDK in any language (6 of 15). 10 + 17 + 14 + 6 + 6 = 53.", "b": "`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." }, "scores": { "a": 53, "b": 71 } }, { "by": 12, "category": "transparency", "leads": "savvycal", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with terms that name SavvyCal, Inc. under Minnesota law and forbid automated access to the site, with the API left to the developer docs (15 of 30). The privacy policy (17 October 2026), DPA (16 January 2023) and processor list (24 October 2026) agree on US hosting, Stripe and return or destruction on termination, but no retention period is stated beyond account lifetime (22 of 30). The developer overview promises additive changes; there is no deprecation policy or dated notice, and the terms allow any feature to change without notice (5 of 20). A processor list with purposes, hosting on Fly.io in Virginia and Crunchy Bridge on AWS us-east, but no locations per processor (15 of 20). 15 + 22 + 5 + 15 = 57.", "b": "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." }, "scores": { "a": 73, "b": 61 } }, { "by": 10, "category": "payments", "leads": "savvycal", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-seat plan prices public, nothing per call (10). A Free plan with the API, webhooks and MCP server included and no card mentioned, though booking through a link needs Basic or Premium and there is no self-serve trial (20). A person signs up in a browser and approves the OAuth consent (0). 0 + 10 + 20 + 0 = 30.", "b": "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." }, "scores": { "a": 30, "b": 20 } }, { "by": 10, "category": "maintenance", "leads": "truto-calendar", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. The newest dated change is the MCP integration of 27 October 2026 on the updates board (30). It is the only dated entry since 7 July, so fewer than three in 90 days (0 of 20). A public updates board, a feature request board and a support address with a stated 24-hour reply within US Central business hours (10 of 15). No official SDKs (0). No package to assess (0). 30 + 0 + 10 + 0 + 0 = 40.", "b": "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." }, "scores": { "a": 40, "b": 50 } }, { "by": 7, "category": "reliability", "leads": "truto-calendar", "name": "Reliability", "reasons": { "a": "Read with the hosted lines. Instatus page at savvycal.instatus.com with App, Microsoft 365, Google Calendar and Integrations components and a month-by-month history (20). No notices from June to November 2026 and 100 per cent App uptime each month, a clean record (30). The only limit with a number is in the OpenAPI spec, 10 event creations a minute per link, failed ones included; nothing covers the rest of the API (7 of 15). That 429 is declared with no Retry-After, backoff guidance or idempotency key, and webhooks are the only place retries are described (3 of 15). No SLA; the terms give the service as is (0). The v1 API is generally available and the MCP server, announced 27 October 2026, is not marked beta (10). 20 + 30 + 7 + 3 + 0 + 10 = 70.", "b": "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." }, "scores": { "a": 70, "b": 77 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "SavvyCal, Inc.", "b": "Yin Yang Inc.", "name": "Vendor" }, { "a": "https://api.savvycal.com/v1", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "63", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-27", "b": "2026-10-26", "name": "Last release" }, { "a": "2026-01-21", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-10-17", "b": "2024-10-19", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Truto Unified Calendar API scores 60.4 (C) on agent readiness against SavvyCal API + MCP's 57 (C), and leads in 5 of 7 scored categories. SavvyCal API + MCP leads on payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, SavvyCal API + MCP or Truto Unified Calendar API?" }, { "answer": "SavvyCal API + MCP takes an API key or an OAuth sign-in. Truto Unified Calendar API needs an API key.", "question": "Do SavvyCal API + MCP and Truto Unified Calendar API need an API key?" }, { "answer": "SavvyCal API + MCP has a hosted endpoint at https://api.savvycal.com/v1. No hosted endpoint is listed for Truto Unified Calendar API.", "question": "Can an agent call SavvyCal API + MCP and Truto Unified Calendar API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 20", "Transparency \u0026 trust, 73 against 61" ], "also": [ "A hosted endpoint, with nothing to install", "Free to start without a card" ], "goodFor": "An agent booking on a person's SavvyCal links or driving their account through the MCP server.", "slug": "savvycal", "watchFor": "No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)" }, { "aheadOn": [ "Reliability, 77 against 70", "Agent ergonomics, 71 against 53", "Maintenance \u0026 community, 50 against 40" ], "also": null, "goodFor": "Software companies that need their product's agent to read and book across customers' Google, Outlook, Cal.com and Calendly accounts.", "slug": "truto-calendar", "watchFor": "Priced from $999 per connector a year with a demo-led sandbox" } ], "history": null, "job": { "capability": "calendar.booking", "name": "Calendar booking" }, "others": [ { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal.json", "title": "Acuity Scheduling API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-truto-calendar.json", "title": "Acuity Scheduling API vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal.json", "title": "Agenda Hero vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/agenda-hero-vs-truto-calendar.json", "title": "Agenda Hero vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/agenda-hero-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-savvycal.json", "title": "Apiroc Unified Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/apiroc-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-truto-calendar.json", "title": "Apiroc Unified Calendar API vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal.json", "title": "Aurinko Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-truto-calendar.json", "title": "Aurinko Calendar API vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-savvycal.json", "title": "Cal.com API v2 + MCP vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/cal-com-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-truto-calendar.json", "title": "Cal.com API v2 + MCP vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/cal-com-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-savvycal.json", "title": "Calendly API + MCP vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/calendly-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-truto-calendar.json", "title": "Calendly API + MCP vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/calendly-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/cozi-vs-savvycal.json", "title": "Cozi Family Organizer vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/cozi-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/cozi-vs-truto-calendar.json", "title": "Cozi Family Organizer vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/cozi-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-savvycal.json", "title": "Cronofy API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/cronofy-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-truto-calendar.json", "title": "Cronofy API vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal.json", "title": "Google Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/google-calendar-api-vs-truto-calendar.json", "title": "Google Calendar API vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal.json", "title": "Microsoft Graph Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-truto-calendar.json", "title": "Microsoft Graph Calendar API vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal.json", "title": "Nylas Calendar and Scheduler API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-truto-calendar.json", "title": "Nylas Calendar and Scheduler API vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/reclaim-ai-vs-savvycal.json", "title": "Reclaim.ai vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/reclaim-ai-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/reclaim-ai-vs-truto-calendar.json", "title": "Reclaim.ai vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/reclaim-ai-vs-truto-calendar" }, { "json": "https://www.anchorterminal.com/compare/truto-calendar-vs-zoom-scheduler.json", "title": "Truto Unified Calendar API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/truto-calendar-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.json", "title": "SavvyCal API + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.json", "title": "SavvyCal API + MCP vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/truto-calendar-vs-youcanbookme.json", "title": "Truto Unified Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/truto-calendar-vs-youcanbookme" } ], "panel": null, "scores": [ { "by": 7, "edge": "truto-calendar", "key": "reliability", "name": "Reliability", "savvycal": 70, "truto-calendar": 77, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "truto-calendar", "key": "schema", "name": "Schema \u0026 documentation", "savvycal": 74, "truto-calendar": 75, "weight": 13 }, { "by": 18, "edge": "truto-calendar", "key": "ergonomics", "name": "Agent ergonomics", "savvycal": 53, "truto-calendar": 71, "weight": 13 }, { "by": 2, "edge": "truto-calendar", "key": "security", "name": "Security \u0026 auth", "savvycal": 50, "truto-calendar": 52, "weight": 14 }, { "by": 10, "edge": "savvycal", "key": "payments", "name": "Payments \u0026 pricing", "savvycal": 30, "truto-calendar": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 10, "edge": "truto-calendar", "key": "maintenance", "name": "Maintenance \u0026 community", "savvycal": 40, "truto-calendar": 50, "weight": 7 }, { "by": 12, "edge": "savvycal", "key": "transparency", "name": "Transparency \u0026 trust", "savvycal": 73, "truto-calendar": 61, "weight": 7 } ], "summary": "Truto Unified Calendar API scores 60.4 (C) on agent readiness against SavvyCal API + MCP's 57 (C), and leads in 5 of 7 scored categories. SavvyCal API + MCP leads on payments \u0026 pricing and transparency \u0026 trust. Both do calendar booking.", "tasks": null, "tutorials": [], "verdicts": { "savvycal": "A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat.", "truto-calendar": "Truto's calendar API is well documented for agents, with Markdown docs, field exclusion, normalised rate-limit headers and errors that name the failing side, across Google, Outlook, Cal.com and Calendly. It is sold from $999 a connector a year through a demo, had an API outage on 29 October 2026 and has no public changelog." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar", "json": "https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar.min.md" }, "markdown": "Truto Unified Calendar API scores 60.4 (C) on agent readiness against SavvyCal API + MCP's 57 (C), and leads in 5 of 7 scored categories. SavvyCal API + MCP leads on payments \u0026 pricing and transparency \u0026 trust. Both do calendar booking.\n\n- SavvyCal API + MCP: grade C, 57/100, rank #815 of 1510. Markdown https://www.anchorterminal.com/tools/savvycal.md · JSON https://www.anchorterminal.com/api/v1/tools/savvycal.json\n- Truto Unified Calendar API: grade C, 60.4/100, rank #655 of 1510. Markdown https://www.anchorterminal.com/tools/truto-calendar.md · JSON https://www.anchorterminal.com/api/v1/tools/truto-calendar.json\n- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md\n- All 118 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md\n\n## Which one, for what\n\n### SavvyCal API + MCP (C)\n\nGood for: An agent booking on a person's SavvyCal links or driving their account through the MCP server.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 20\n- Transparency \u0026 trust, 73 against 61\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)\n\n### Truto Unified Calendar API (C)\n\nGood for: Software companies that need their product's agent to read and book across customers' Google, Outlook, Cal.com and Calendly accounts.\n\nAhead on:\n- Reliability, 77 against 70\n- Agent ergonomics, 71 against 53\n- Maintenance \u0026 community, 50 against 40\n\nWatch for: Priced from $999 per connector a year with a demo-led sandbox\n\n\n## Why the edge\n\n### Agent ergonomics: Truto Unified Calendar API +18\n\n- SavvyCal API + MCP (53): List responses are sized by `limit` (default 20, at most 100) with no field selection. The MCP server lists 63 tools with no documented toolset or read-only list, though a client can ask for the `mcp:read` scope alone (10 of 25). Cursor pagination with `after`, `before` and `limit`, and date and status filters on events (17 of 20). Errors name the field, the failed validation and a limit count, which an agent can act on, but a 429 carries no wait time (14 of 20). No idempotency key on booking or link creation, and the MCP annotations could not be read; the docs say the assistant confirms before cancelling, deleting or inviting (6 of 20). Creating an event needs five fields, and there is no official SDK in any language (6 of 15). 10 + 17 + 14 + 6 + 6 = 53.\n- 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.\n\n### Transparency \u0026 trust: SavvyCal API + MCP +12\n\n- SavvyCal API + MCP (73): Closed service with terms that name SavvyCal, Inc. under Minnesota law and forbid automated access to the site, with the API left to the developer docs (15 of 30). The privacy policy (17 October 2026), DPA (16 January 2023) and processor list (24 October 2026) agree on US hosting, Stripe and return or destruction on termination, but no retention period is stated beyond account lifetime (22 of 30). The developer overview promises additive changes; there is no deprecation policy or dated notice, and the terms allow any feature to change without notice (5 of 20). A processor list with purposes, hosting on Fly.io in Virginia and Crunchy Bridge on AWS us-east, but no locations per processor (15 of 20). 15 + 22 + 5 + 15 = 57.\n- 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.\n\n### Payments \u0026 pricing: SavvyCal API + MCP +10\n\n- SavvyCal API + MCP (30): No x402, MPP or L402 (0). Per-seat plan prices public, nothing per call (10). A Free plan with the API, webhooks and MCP server included and no card mentioned, though booking through a link needs Basic or Premium and there is no self-serve trial (20). A person signs up in a browser and approves the OAuth consent (0). 0 + 10 + 20 + 0 = 30.\n- 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.\n\n### Maintenance \u0026 community: Truto Unified Calendar API +10\n\n- SavvyCal API + MCP (40): Read as a closed service. The newest dated change is the MCP integration of 27 October 2026 on the updates board (30). It is the only dated entry since 7 July, so fewer than three in 90 days (0 of 20). A public updates board, a feature request board and a support address with a stated 24-hour reply within US Central business hours (10 of 15). No official SDKs (0). No package to assess (0). 30 + 0 + 10 + 0 + 0 = 40.\n- 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.\n\n### Reliability: Truto Unified Calendar API +7\n\n- SavvyCal API + MCP (70): Read with the hosted lines. Instatus page at savvycal.instatus.com with App, Microsoft 365, Google Calendar and Integrations components and a month-by-month history (20). No notices from June to November 2026 and 100 per cent App uptime each month, a clean record (30). The only limit with a number is in the OpenAPI spec, 10 event creations a minute per link, failed ones included; nothing covers the rest of the API (7 of 15). That 429 is declared with no Retry-After, backoff guidance or idempotency key, and webhooks are the only place retries are described (3 of 15). No SLA; the terms give the service as is (0). The v1 API is generally available and the MCP server, announced 27 October 2026, is not marked beta (10). 20 + 30 + 7 + 3 + 0 + 10 = 70.\n- 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.\n\n## Score by category\n\n| Category | Weight | SavvyCal API + MCP | Truto Unified Calendar API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 77 | Truto Unified Calendar API +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 75 | Truto Unified Calendar API +1 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 71 | Truto Unified Calendar API +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 50 | 52 | Truto Unified Calendar API +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | SavvyCal API + MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 40 | 50 | Truto Unified Calendar API +10 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 73 | 61 | SavvyCal API + MCP +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57 · C** | **60.4 · C** | |\n\n## Facts side by side\n\n| Fact | SavvyCal API + MCP | Truto Unified Calendar API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | SavvyCal, Inc. | Yin Yang Inc. |\n| Hosted endpoint | `https://api.savvycal.com/v1` | no (local only) |\n| Transports | HTTP, Streamable HTTP | |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Tools exposed | 63 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-27 | 2026-10-26 |\n| Terms last updated | 2026-01-21 | no date given |\n| Privacy policy last updated | 2026-10-17 | 2024-10-19 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n\n## Verdicts\n\n**SavvyCal API + MCP.** A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat.\n\n**Truto Unified Calendar API.** Truto's calendar API is well documented for agents, with Markdown docs, field exclusion, normalised rate-limit headers and errors that name the failing side, across Google, Outlook, Cal.com and Calendly. It is sold from $999 a connector a year through a demo, had an API outage on 29 October 2026 and has no public changelog.\n\n## Before you call either\n\n### SavvyCal API + MCP\n\n1. Call GET /v1/links/{link_id}/slots with `from` and `until` (at most 31 days apart) and book only a returned slot; POST /v1/links/{link_id}/events refuses other times with 422\n2. Keep event creation under 10 requests a minute per link, failed attempts included, or expect 429 with no Retry-After\n3. Page with the `after` and `before` cursors from `metadata` and `limit` up to 100; an invalid filter value resets every filter to its default\n4. Connect the MCP server with a client that supports dynamic client registration, and request `mcp:read` when the task only reads\n5. Verify webhooks with HMAC-SHA256 over the raw body against `x-savvycal-signature` and answer 2xx quickly\n\n### Truto Unified Calendar API\n\n1. Pass `integrated_account_id` on every call; the token alone reaches nothing\n2. Call the meta endpoint for the method first to see which filters the vendor supports\n3. Set `truto_ignore_remote_data=true` and list fields in `truto_exclude_fields` to keep responses small\n4. On 429 wait for Retry-After; stay under 50 requests every 10 seconds per integrated account\n5. Set `expand_recurring=true` when the task needs each instance of a repeating event\n\n## Questions\n\n### Which is better for AI agents, SavvyCal API + MCP or Truto Unified Calendar API?\n\nTruto Unified Calendar API scores 60.4 (C) on agent readiness against SavvyCal API + MCP's 57 (C), and leads in 5 of 7 scored categories. SavvyCal API + MCP leads on payments \u0026 pricing and transparency \u0026 trust.\n\n### Do SavvyCal API + MCP and Truto Unified Calendar API need an API key?\n\nSavvyCal API + MCP takes an API key or an OAuth sign-in. Truto Unified Calendar API needs an API key.\n\n### Can an agent call SavvyCal API + MCP and Truto Unified Calendar API without installing anything?\n\nSavvyCal API + MCP has a hosted endpoint at https://api.savvycal.com/v1. No hosted endpoint is listed for Truto Unified Calendar API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar.json, and with the fewest tokens: https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"savvycal\", \"b\": \"truto-calendar\"}`. From a terminal: `anchor compare savvycal truto-calendar`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/savvycal.json and https://www.anchorterminal.com/api/v1/tools/truto-calendar.json\n\n## Other comparisons with SavvyCal API + MCP or Truto Unified Calendar API\n\n- [Acuity Scheduling API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal.md)\n- [Acuity Scheduling API vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-truto-calendar.md)\n- [Agenda Hero vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal.md)\n- [Agenda Hero vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/agenda-hero-vs-truto-calendar.md)\n- [Apiroc Unified Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/apiroc-vs-savvycal.md)\n- [Apiroc Unified Calendar API vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-truto-calendar.md)\n- [Aurinko Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal.md)\n- [Aurinko Calendar API vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-truto-calendar.md)\n- [Cal.com API v2 + MCP vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cal-com-vs-savvycal.md)\n- [Cal.com API v2 + MCP vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/cal-com-vs-truto-calendar.md)\n- [Calendly API + MCP vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/calendly-vs-savvycal.md)\n- [Calendly API + MCP vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/calendly-vs-truto-calendar.md)\n- [Cozi Family Organizer vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cozi-vs-savvycal.md)\n- [Cozi Family Organizer vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/cozi-vs-truto-calendar.md)\n- [Cronofy API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cronofy-vs-savvycal.md)\n- [Cronofy API vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/cronofy-vs-truto-calendar.md)\n- [Google Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal.md)\n- [Google Calendar API vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/google-calendar-api-vs-truto-calendar.md)\n- [Microsoft Graph Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal.md)\n- [Microsoft Graph Calendar API vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-truto-calendar.md)\n- [Nylas Calendar and Scheduler API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal.md)\n- [Nylas Calendar and Scheduler API vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/nylas-calendar-vs-truto-calendar.md)\n- [Reclaim.ai vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/reclaim-ai-vs-savvycal.md)\n- [Reclaim.ai vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/reclaim-ai-vs-truto-calendar.md)\n- [Truto Unified Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/truto-calendar-vs-zoom-scheduler.md)\n- [SavvyCal API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.md)\n- [SavvyCal API + MCP vs Zoom Scheduler API](https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.md)\n- [Truto Unified Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/truto-calendar-vs-youcanbookme.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "SavvyCal API + MCP vs Truto Unified Calendar API", "url": "" } ], "description": "Truto Unified Calendar scores 60.4 (C) to SavvyCal's 57 (C) for calendar booking. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "SavvyCal API + MCP C 57", "Truto Unified Calendar API C 60.4", "scores" ], "h1": "SavvyCal API + MCP vs Truto Unified Calendar API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/savvycal-vs-truto-calendar", "published": "2026-10-01", "section": "tools", "title": "SavvyCal vs Truto Unified Calendar for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar" }, "tokens": { "markdown": 4300, "slim": 2180 }, "version": 1 }