{ "data": { "a": { "slug": "nylas-calendar", "name": "Nylas Calendar and Scheduler API", "vendor": "Nylas", "vendorUrl": "https://www.nylas.com", "kind": "http-api", "category": "scheduling", "summary": "Unified calendar API over Google, Microsoft 365 and Outlook, Exchange (EWS) and iCloud.", "url": "https://www.anchorterminal.com/tools/nylas-calendar", "markdownUrl": "https://www.anchorterminal.com/tools/nylas-calendar.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nylas-calendar.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nylas-calendar.json", "dns": "nylas-calendar.grade.anchorterminal.com", "repo": "https://github.com/nylas/nylas-nodejs", "license": "MIT (SDKs)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.us.nylas.com/v3", "packages": [ { "registry": "npm", "name": "nylas" }, { "registry": "pypi", "name": "nylas" } ], "auth": "mixed", "authNotes": "Application API key or a Nylas IAM API key as a Bearer token. IAM keys (since 6 October 2026) are bound to one grant, workspace, application or organisation with roles and permissions, and always expire. Each connected user is a grant, created through Nylas hosted OAuth or your own provider credentials, and addressed as /v3/grants/\u003cgrant_id\u003e. The hosted MCP takes either key in the `Authorization` header.", "pricing": "freemium", "pricingNotes": "Free $0 with 5 email and calendar connected accounts, 5 Notetaker bot hours and 3 Agent Accounts, no credit card. Essentials $15 a month with 10 email and calendar accounts ($2.25 each after), 10 calendar-only accounts ($1.70 each after), 10 Notetaker hours then $0.80 an hour, and 10 Agent Accounts. Pro $49 a month ($43 annual) with 25 email and calendar accounts ($2.00 each after, $1.75 annual), 35 calendar-only accounts ($1.50 each after, $1.35 annual), 70 Notetaker hours then $0.70 an hour, and 50 Agent Accounts. Enterprise is custom, with a 99.99% availability SLA on annual contracts (https://www.nylas.com/pricing/).", "priceSummary": "$15 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 38, "popularity": { "githubStars": 181, "npmWeekly": 281223, "pypiWeekly": 103888, "asOf": "2026-09-30" }, "docsUrl": "https://developer.nylas.com/docs/v3/calendar/", "llmsTxt": "https://developer.nylas.com/llms.txt", "openapi": "https://developer.nylas.com/openapi.json", "capabilities": [ "calendar.read", "calendar.write", "calendar.availability", "calendar.booking", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "llms-txt", "openapi", "webhooks", "typescript", "python", "enterprise", "eu", "closed-source" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 75.5, "grade": "BB", "agentReady": true, "rank": 60, "ranked": true, "rankOf": 1510, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 88, "payments": 40, "reliability": 72, "schema": 91, "security": 85, "transparency": 82 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars, and since 6 October IAM keys can limit an agent to one calendar grant with chosen permissions. Event writes take no idempotency key, and the MCP's confirmation step covers email sends, not event changes or deletions.", "bestFor": "Products that need read, write and availability across every major provider plus email on one grant, from a handful of users upwards.", "strengths": [ "One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars", "IAM API keys bind an agent to one grant with chosen permissions, always expire and are logged for 400 days", "Free plan with 5 connected accounts and no card", "MCP docs warn about hidden instructions in calendar events and tell agents to treat them as untrusted", "OpenAPI 3.1 file with 244 operations and a dated changelog with 20 entries between 15 September and 30 October 2026" ], "weaknesses": [ "Application API keys still reach every grant, and the IAM pages name no calendar permission", "No idempotency key on event writes, only on email send", "The MCP's confirmation step covers email sends only, not event creation, updates or deletion", "Delayed or missing webhooks across all providers for about five hours on 19 August 2026", "38 MCP tools load at once with no toolsets, so a calendar-only agent carries the email tools too" ], "agentNotes": [ "Address calendar calls to /v3/grants/\u003cgrant_id\u003e, one grant per connected account", "Use an IAM API key bound to the one grant the agent needs rather than the application key", "List events in the window before retrying a create, since event writes have no idempotency key", "Keep availability requests within 732 days, the cap since 10 October 2026", "On 429, use the passed-through `Retry-After` if present, otherwise back off per grant" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 75.5 } ], "editorialScores": { "ergonomics": 71, "maintenance": 88, "payments": 40, "reliability": 72, "schema": 91, "security": 85, "transparency": 67 }, "provenanceScore": 96, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.us.nylas.com/v3/grants/$NYLAS_GRANT_ID/calendars?limit=5\" \\\n -H \"Authorization: Bearer $NYLAS_API_KEY\"", "claudeCode": "claude mcp add --transport http nylas https://mcp.us.nylas.com --header \"Authorization: Bearer $NYLAS_API_KEY\"", "config": { "mcpServers": { "nylas": { "headers": { "Authorization": "Bearer ${NYLAS_API_KEY}" }, "url": "https://mcp.us.nylas.com" } } } }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/nylas-calendar" }, "sameCompany": [ "nylas-notetaker", "nylas-email" ], "area": "everyday", "unitPrices": [ { "item": "Essentials", "unit": "month", "usd": 15, "note": "10 email and calendar plus 10 calendar-only accounts" }, { "item": "Pro", "unit": "month", "usd": 49, "note": "25 email and calendar plus 35 calendar-only accounts, billed monthly" }, { "item": "Extra calendar-only account on Essentials", "unit": "account-month", "usd": 1.7 }, { "item": "Extra calendar-only account on Pro", "unit": "account-month", "usd": 1.5 }, { "item": "Extra calendar-only account on Pro annual", "unit": "account-month", "usd": 1.35 }, { "item": "Extra email and calendar account on Essentials", "unit": "account-month", "usd": 2.25 }, { "item": "Extra email and calendar account on Pro", "unit": "account-month", "usd": 2 }, { "item": "Extra Agent Account on Pro", "unit": "account-month", "usd": 0.4 } ], "provenance": { "legalEntity": "Nylas, Inc.", "domain": "nylas.com", "domainRegistered": "2001-11-07", "domainNote": "nylas.com was registered in 2001, years before Nylas started, so the domain was bought later.", "endpointOnVendorDomain": true, "terms": "https://www.nylas.com/legal/terms/", "privacy": "https://www.nylas.com/privacy-policy/", "statusPage": "https://status-v3.nylas.com", "changelog": "https://developer.nylas.com/docs/changelogs/", "securityTxt": "valid", "checked": "2026-11-01", "notes": [ "The terms (updated 23 June 2025) name Nylas, Inc. in Palo Alto, California, under California law with arbitration.", "developer.nylas.com/.well-known/security.txt is an RFC 9116 file with security@nylas.com as contact and Policy https://www.nylas.com/security/, expiring on 1 August 2027. www.nylas.com/.well-known/security.txt returns 404.", "The status page for the v3 API is status-v3.nylas.com." ], "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nylas-calendar.json", "live": { "slug": "nylas-calendar", "probe": { "target": "https://api.us.nylas.com/v3", "method": "get", "lastAt": "2026-11-07T19:22:22.708784601Z", "lastOk": true, "lastStatus": 404, "lastMs": 194, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 174, "p95ms24h": 267, "samples24h": 238, "samples30d": 7920, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "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://status-v3.nylas.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:47.387631233Z" }, "versions": [ { "registry": "github", "name": "nylas/nylas-nodejs", "version": "v8.5.0", "released": "2026-11-04", "seenAt": "2026-11-06T23:50:21.332450526Z" }, { "registry": "npm", "name": "nylas", "version": "8.5.0", "seenAt": "2026-11-06T23:50:19.761035145Z" }, { "registry": "pypi", "name": "nylas", "version": "6.19.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:50:21.042433624Z" } ], "githubStars": 180, "npmWeekly": 612065, "pypiWeekly": 96230, "securityTxt": { "url": "https://nylas.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:15.656972229Z" }, "llmsTxt": { "url": "https://developer.nylas.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:20.562490094Z" }, "domain": { "domain": "nylas.com", "registered": "2001-11-07", "source": "https://rdap.verisign.com/com/v1/domain/nylas.com", "checkedAt": "2026-11-01T14:23:35.373653199Z" }, "pages": [ { "url": "https://developer.nylas.com/docs/changelogs/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:03:13.07951388Z", "changedAt": "2026-10-31T06:07:27.740116772Z", "fingerprint": "bd9a2008a70b" }, { "url": "https://developer.nylas.com/docs/changelogs/2026-10-10-availability-metadata-and-provider-fixes/", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:03:17.330684388Z", "changedAt": "2026-10-31T06:07:31.93033799Z", "fingerprint": "f39b8f77f7ec" }, { "url": "https://www.nylas.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:32:11.502822065Z", "changedAt": "2026-10-30T05:58:26.391023995Z", "fingerprint": "7331ddea70df" }, { "url": "https://www.nylas.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:32:12.128545591Z", "changedAt": "2026-10-30T05:58:26.881176912Z", "fingerprint": "98943bc01feb" }, { "url": "https://www.nylas.com/legal/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:32:07.069803388Z", "changedAt": "2026-10-30T05:58:21.745601982Z", "fingerprint": "97e8708900a7" } ], "mcpTools": { "url": "https://mcp.us.nylas.com", "checkedAt": "2026-11-07T01:46:29.25362886Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:29.25362886Z" }, "github": { "repo": "nylas/nylas-nodejs", "checkedAt": "2026-11-02T09:11:28.143578213Z", "stars": 181, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-21T18:59:14Z", "openIssues": 4, "openPRs": 4, "issuesOpened90d": 1, "issuesClosed90d": 0, "prsMerged90d": 4, "ci": { "branch": "main", "runs": 50, "success": 49, "failure": 1, "other": 0, "latest": "success", "latestAt": "2026-10-13T16:22:32Z" }, "replies": { "sampled": 25, "unanswered": 3, "medianDays": 10 } }, "updatedAt": "2026-11-07T19:22:22.708784601Z" } }, "answer": "Nylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against Truto Unified Calendar API's 60.4 (C), and leads in 5 of 7 scored categories. Truto Unified Calendar API leads on reliability.", "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": 38, "category": "maintenance", "leads": "nylas-calendar", "name": "Maintenance \u0026 community", "reasons": { "a": "Changelog entries up to 30 October 2026, the last calendar-specific one on 22 October with event webhook, recurring cancellation and Microsoft availability fixes (30). 20 dated changelog entries between 15 September and 30 October (20). Public dated changelog, open SDK repositories with commits to 30 September (Python) and 13 October (Node), and support (15). Current official SDKs (15). nylas-python v6.18.0 on 30 September 2026. The Node SDK's package.json is still 8.4.0 (24 June 2026) with unreleased commits on main to 13 October (8). 30+20+15+15+8 = 88.", "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": 88, "b": 50 } }, { "by": 33, "category": "security", "leads": "nylas-calendar", "name": "Security \u0026 auth", "reasons": { "a": "Nylas IAM, launched 6 October 2026, issues API keys bound to one grant, workspace, application or organisation with roles and permissions. Every new IAM key expires, keys can be disabled or rotated, and the IAM guide (re-read 1 November) shows principals and credentials created and rotated through a public /v3/iam API once a first management key is made in the Dashboard. End users connect through OAuth with scopes the app picks. Application keys still reach every grant, so 1 is held back as for nylas-email, and 1 more because the IAM pages name no calendar permission, as nylas-notetaker holds back for Notetaker (28). A principal can be bound to one grant with read permissions, the agent security page shows a scheduling agent limited to reading calendars and creating events, and anything outside the binding answers 403. The MCP confirmation step covers email sends only, so creating, updating or deleting an event needs no confirmation. 3 below nylas-email's 17, which has the send confirmation (14). The MCP and agent security docs say event descriptions and locations can carry hidden instructions and tell agents to treat calendar content as untrusted (13). IAM Access Activity records allowed and denied API, authentication and MCP requests for 400 days with links to request logs, and Dashboard logs are kept 14 days. Requests made with an application key appear only in the logs (13). SOC 2 Type II, ISO 27001 and 27701, CSA STAR, an annual penetration test and a private bug bounty with security@nylas.com, per the 1 October check, and an RFC 9116 security.txt on developer.nylas.com valid to 1 August 2027. www.nylas.com still has none. nylas-email scores this 17 (17). 28+14+13+13+17 = 85.", "b": "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." }, "scores": { "a": 85, "b": 52 } }, { "by": 21, "category": "transparency", "leads": "nylas-calendar", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under Californian law, with MIT SDKs (15). The privacy policy keeps customer data for the life of the account plus two months and lets EEA customers pick UK or US data centres, per the 1 October check and as nylas-email read it on 1 November. A sub-processor page dated 28 August 2026, with changes announced on the status page (24). v2 deprecation documented and a dated changelog, but no deprecation policy found. The 10 October changelog capped availability ranges at 732 days on the day it took effect (10). Sub-processors listed, AWS and GCP named as hosts, US and EU regions (18). 15+24+10+18 = 67.", "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": 82, "b": 61 } }, { "by": 20, "category": "payments", "leads": "nylas-calendar", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-account prices published without login, such as $1.50 a calendar-only account a month on Pro monthly and $1.35 on annual, re-read 1 November (20). Free plan with 5 connected accounts, \"No credit card required\" (20). Keys can be minted by API, but only after a person makes a first management key in the Dashboard after a browser signup, and each calendar owner completes OAuth (0). 0+20+20+0 = 40.", "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": 40, "b": 20 } }, { "by": 16, "category": "schema", "leads": "nylas-calendar", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 file at developer.nylas.com/openapi.json with 140 paths and 244 operations on 1 November, 20 of the paths and 34 operations for calendars, events, availability and scheduling (25). llms.txt and Markdown docs (10). Guides say when to use each API, and the MCP page lists each tool with a one-line purpose and no when-not-to guidance (15). Typed parameters in the reference (12). An errors page with a JSON shape (`type`, `message`, `provider_error`, `request_id`) and a retry yes or no for each status code (14). v3 in the path and a dated changelog with 20 entries between 15 September and 30 October 2026 (15). 25+10+15+12+14+15 = 91.", "b": "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." }, "scores": { "a": 91, "b": 75 } }, { "by": 5, "category": "reliability", "leads": "truto-calendar", "name": "Reliability", "reasons": { "a": "Atlassian Statuspage at status-v3.nylas.com with US and EU components (20). In the 90 days from 3 August the history feed names no calendar incident. Incidents hit IMAP message reads (6 August), US message sync latency (11 August), EWS attachments (14 August), Microsoft send and read through Exchange Online (31 August to 1 September), Notetaker Teams joins (4 September), IMAP retrieval (10 September), IMAP sync (17 September) and Microsoft 365 sign-in for Sandbox applications on shared credentials (from 22 October), each limited to one provider, product or non-production surface, so partial. The exception is 19 August, delayed or missing webhooks for all providers in the US and EU from 09:11 to 14:34 PDT, mitigated by recovering the sync state of affected grants. Calendar event webhooks come from the same provider grant sync, so it counts here as one major, as for nylas-email (10). 200 requests a second per grant for calendar and 50 a second per application for grant, auth and webhook endpoints, plus the provider limits behind them, re-read on 1 November (15). 429s separate Nylas limits from provider limits and pass on the provider's Retry-After, Google's included since 22 October, and the errors page says which codes to retry with exponential backoff. Idempotency keys cover email send only, not event writes (10). The pricing page lists a 99.99 per cent availability SLA for annual Enterprise contracts, with terms in the customer agreement, which nylas-email scores 7 (7). GA (10). 20+10+15+10+7+10 = 72.", "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": 72, "b": 77 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Nylas", "b": "Yin Yang Inc.", "name": "Vendor" }, { "a": "https://api.us.nylas.com/v3", "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": "MIT (SDKs)", "b": "none", "name": "Licence" }, { "a": "38", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-10-26", "name": "Last release" }, { "a": "2025-06-23", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-01-06", "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": "not found in the text", "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" }, { "a": "181 stars, 281k npm/wk, 104k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Nylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against Truto Unified Calendar API's 60.4 (C), and leads in 5 of 7 scored categories. Truto Unified Calendar API leads on reliability.", "question": "Which is better for AI agents, Nylas Calendar and Scheduler API or Truto Unified Calendar API?" }, { "answer": "Nylas Calendar and Scheduler API takes an API key or an OAuth sign-in. Truto Unified Calendar API needs an API key.", "question": "Do Nylas Calendar and Scheduler API and Truto Unified Calendar API need an API key?" }, { "answer": "Nylas Calendar and Scheduler API has a hosted endpoint at https://api.us.nylas.com/v3. No hosted endpoint is listed for Truto Unified Calendar API.", "question": "Can an agent call Nylas Calendar and Scheduler API and Truto Unified Calendar API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 91 against 75", "Security \u0026 auth, 85 against 52", "Payments \u0026 pricing, 40 against 20", "Maintenance \u0026 community, 88 against 50", "Transparency \u0026 trust, 82 against 61" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "Free to start without a card" ], "goodFor": "Products that need read, write and availability across every major provider plus email on one grant, from a handful of users upwards.", "slug": "nylas-calendar", "watchFor": "Application API keys still reach every grant, and the IAM pages name no calendar permission" }, { "aheadOn": [ "Reliability, 77 against 72" ], "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": { "nylas-calendar": [ { "causes": [ "product", "correction" ], "date": "2026-11-01", "delta": 4.4, "from": 71.1, "fromGrade": "BB", "to": 75.5, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 71, "fromGrade": "BB", "to": 71.1, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 71.3, "fromGrade": "BB", "to": 71, "toGrade": "BB" } ], "truto-calendar": null }, "job": { "capability": "calendar.read", "name": "Calendar access" }, "others": [ { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar.json", "title": "Acuity Scheduling API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar" }, { "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-nylas-calendar.json", "title": "Agenda Hero vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/agenda-hero-vs-nylas-calendar" }, { "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-nylas-calendar.json", "title": "Apiroc Unified Calendar API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-nylas-calendar" }, { "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-nylas-calendar.json", "title": "Aurinko Calendar API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar" }, { "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-nylas-calendar.json", "title": "Cal.com API v2 + MCP vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/cal-com-vs-nylas-calendar" }, { "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-nylas-calendar.json", "title": "Calendly API + MCP vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar" }, { "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-nylas-calendar.json", "title": "Cozi Family Organizer vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/cozi-vs-nylas-calendar" }, { "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-nylas-calendar.json", "title": "Cronofy API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-nylas-calendar" }, { "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-nylas-calendar.json", "title": "Google Calendar API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-nylas-calendar" }, { "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-nylas-calendar.json", "title": "Microsoft Graph Calendar API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-nylas-calendar" }, { "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-reclaim-ai.json", "title": "Nylas Calendar and Scheduler API vs Reclaim.ai", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-reclaim-ai" }, { "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-zoom-scheduler.json", "title": "Nylas Calendar and Scheduler API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler" }, { "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/nylas-calendar-vs-youcanbookme.json", "title": "Nylas Calendar and Scheduler API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar.json", "title": "SavvyCal API + MCP vs Truto Unified Calendar API", "url": "https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar" }, { "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": 5, "edge": "truto-calendar", "key": "reliability", "name": "Reliability", "nylas-calendar": 72, "truto-calendar": 77, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 16, "edge": "nylas-calendar", "key": "schema", "name": "Schema \u0026 documentation", "nylas-calendar": 91, "truto-calendar": 75, "weight": 13 }, { "by": 0, "edge": "", "key": "ergonomics", "name": "Agent ergonomics", "nylas-calendar": 71, "truto-calendar": 71, "weight": 13 }, { "by": 33, "edge": "nylas-calendar", "key": "security", "name": "Security \u0026 auth", "nylas-calendar": 85, "truto-calendar": 52, "weight": 14 }, { "by": 20, "edge": "nylas-calendar", "key": "payments", "name": "Payments \u0026 pricing", "nylas-calendar": 40, "truto-calendar": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 38, "edge": "nylas-calendar", "key": "maintenance", "name": "Maintenance \u0026 community", "nylas-calendar": 88, "truto-calendar": 50, "weight": 7 }, { "by": 21, "edge": "nylas-calendar", "key": "transparency", "name": "Transparency \u0026 trust", "nylas-calendar": 82, "truto-calendar": 61, "weight": 7 } ], "summary": "Nylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against Truto Unified Calendar API's 60.4 (C), and leads in 5 of 7 scored categories. Truto Unified Calendar API leads on reliability. Both do calendar access.", "tasks": null, "tutorials": [], "verdicts": { "nylas-calendar": "One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars, and since 6 October IAM keys can limit an agent to one calendar grant with chosen permissions. Event writes take no idempotency key, and the MCP's confirmation step covers email sends, not event changes or deletions.", "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/nylas-calendar-vs-truto-calendar", "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-truto-calendar.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/nylas-calendar-vs-truto-calendar.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/nylas-calendar-vs-truto-calendar.min.md" }, "markdown": "Nylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against Truto Unified Calendar API's 60.4 (C), and leads in 5 of 7 scored categories. Truto Unified Calendar API leads on reliability. Both do calendar access.\n\n- Nylas Calendar and Scheduler API: grade BB, 75.5/100, rank #60 of 1510. Markdown https://www.anchorterminal.com/tools/nylas-calendar.md · JSON https://www.anchorterminal.com/api/v1/tools/nylas-calendar.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### Nylas Calendar and Scheduler API (BB)\n\nGood for: Products that need read, write and availability across every major provider plus email on one grant, from a handful of users upwards.\n\nAhead on:\n- Schema \u0026 documentation, 91 against 75\n- Security \u0026 auth, 85 against 52\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 88 against 50\n- Transparency \u0026 trust, 82 against 61\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: Application API keys still reach every grant, and the IAM pages name no calendar permission\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 72\n\nWatch for: Priced from $999 per connector a year with a demo-led sandbox\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Nylas Calendar and Scheduler API +38\n\n- Nylas Calendar and Scheduler API (88): Changelog entries up to 30 October 2026, the last calendar-specific one on 22 October with event webhook, recurring cancellation and Microsoft availability fixes (30). 20 dated changelog entries between 15 September and 30 October (20). Public dated changelog, open SDK repositories with commits to 30 September (Python) and 13 October (Node), and support (15). Current official SDKs (15). nylas-python v6.18.0 on 30 September 2026. The Node SDK's package.json is still 8.4.0 (24 June 2026) with unreleased commits on main to 13 October (8). 30+20+15+15+8 = 88.\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### Security \u0026 auth: Nylas Calendar and Scheduler API +33\n\n- Nylas Calendar and Scheduler API (85): Nylas IAM, launched 6 October 2026, issues API keys bound to one grant, workspace, application or organisation with roles and permissions. Every new IAM key expires, keys can be disabled or rotated, and the IAM guide (re-read 1 November) shows principals and credentials created and rotated through a public /v3/iam API once a first management key is made in the Dashboard. End users connect through OAuth with scopes the app picks. Application keys still reach every grant, so 1 is held back as for nylas-email, and 1 more because the IAM pages name no calendar permission, as nylas-notetaker holds back for Notetaker (28). A principal can be bound to one grant with read permissions, the agent security page shows a scheduling agent limited to reading calendars and creating events, and anything outside the binding answers 403. The MCP confirmation step covers email sends only, so creating, updating or deleting an event needs no confirmation. 3 below nylas-email's 17, which has the send confirmation (14). The MCP and agent security docs say event descriptions and locations can carry hidden instructions and tell agents to treat calendar content as untrusted (13). IAM Access Activity records allowed and denied API, authentication and MCP requests for 400 days with links to request logs, and Dashboard logs are kept 14 days. Requests made with an application key appear only in the logs (13). SOC 2 Type II, ISO 27001 and 27701, CSA STAR, an annual penetration test and a private bug bounty with security@nylas.com, per the 1 October check, and an RFC 9116 security.txt on developer.nylas.com valid to 1 August 2027. www.nylas.com still has none. nylas-email scores this 17 (17). 28+14+13+13+17 = 85.\n- 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.\n\n### Transparency \u0026 trust: Nylas Calendar and Scheduler API +21\n\n- Nylas Calendar and Scheduler API (82): Closed service under Californian law, with MIT SDKs (15). The privacy policy keeps customer data for the life of the account plus two months and lets EEA customers pick UK or US data centres, per the 1 October check and as nylas-email read it on 1 November. A sub-processor page dated 28 August 2026, with changes announced on the status page (24). v2 deprecation documented and a dated changelog, but no deprecation policy found. The 10 October changelog capped availability ranges at 732 days on the day it took effect (10). Sub-processors listed, AWS and GCP named as hosts, US and EU regions (18). 15+24+10+18 = 67.\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: Nylas Calendar and Scheduler API +20\n\n- Nylas Calendar and Scheduler API (40): No x402, MPP or L402 (0). Per-account prices published without login, such as $1.50 a calendar-only account a month on Pro monthly and $1.35 on annual, re-read 1 November (20). Free plan with 5 connected accounts, \"No credit card required\" (20). Keys can be minted by API, but only after a person makes a first management key in the Dashboard after a browser signup, and each calendar owner completes OAuth (0). 0+20+20+0 = 40.\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### Schema \u0026 documentation: Nylas Calendar and Scheduler API +16\n\n- Nylas Calendar and Scheduler API (91): OpenAPI 3.1 file at developer.nylas.com/openapi.json with 140 paths and 244 operations on 1 November, 20 of the paths and 34 operations for calendars, events, availability and scheduling (25). llms.txt and Markdown docs (10). Guides say when to use each API, and the MCP page lists each tool with a one-line purpose and no when-not-to guidance (15). Typed parameters in the reference (12). An errors page with a JSON shape (`type`, `message`, `provider_error`, `request_id`) and a retry yes or no for each status code (14). v3 in the path and a dated changelog with 20 entries between 15 September and 30 October 2026 (15). 25+10+15+12+14+15 = 91.\n- 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.\n\n### Reliability: Truto Unified Calendar API +5\n\n- Nylas Calendar and Scheduler API (72): Atlassian Statuspage at status-v3.nylas.com with US and EU components (20). In the 90 days from 3 August the history feed names no calendar incident. Incidents hit IMAP message reads (6 August), US message sync latency (11 August), EWS attachments (14 August), Microsoft send and read through Exchange Online (31 August to 1 September), Notetaker Teams joins (4 September), IMAP retrieval (10 September), IMAP sync (17 September) and Microsoft 365 sign-in for Sandbox applications on shared credentials (from 22 October), each limited to one provider, product or non-production surface, so partial. The exception is 19 August, delayed or missing webhooks for all providers in the US and EU from 09:11 to 14:34 PDT, mitigated by recovering the sync state of affected grants. Calendar event webhooks come from the same provider grant sync, so it counts here as one major, as for nylas-email (10). 200 requests a second per grant for calendar and 50 a second per application for grant, auth and webhook endpoints, plus the provider limits behind them, re-read on 1 November (15). 429s separate Nylas limits from provider limits and pass on the provider's Retry-After, Google's included since 22 October, and the errors page says which codes to retry with exponential backoff. Idempotency keys cover email send only, not event writes (10). The pricing page lists a 99.99 per cent availability SLA for annual Enterprise contracts, with terms in the customer agreement, which nylas-email scores 7 (7). GA (10). 20+10+15+10+7+10 = 72.\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 | Nylas Calendar and Scheduler API | Truto Unified Calendar API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 77 | Truto Unified Calendar API +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 91 | 75 | Nylas Calendar and Scheduler API +16 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 71 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 85 | 52 | Nylas Calendar and Scheduler API +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 20 | Nylas Calendar and Scheduler API +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 88 | 50 | Nylas Calendar and Scheduler API +38 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 82 | 61 | Nylas Calendar and Scheduler API +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **75.5 · BB** | **60.4 · C** | |\n\n## Facts side by side\n\n| Fact | Nylas Calendar and Scheduler API | Truto Unified Calendar API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Nylas | Yin Yang Inc. |\n| Hosted endpoint | `https://api.us.nylas.com/v3` | no (local only) |\n| Transports | HTTP, Streamable HTTP | |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | MIT (SDKs) | none |\n| Tools exposed | 38 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-30 | 2026-10-26 |\n| Terms last updated | 2025-06-23 | no date given |\n| Privacy policy last updated | 2026-01-06 | 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 | not found in the text | 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| Popularity | 181 stars, 281k npm/wk, 104k PyPI/wk | none |\n| Agent reviews | 3/5 (2) | none |\n\n## How the scores have moved\n\n### Nylas Calendar and Scheduler API\n\n- +4.4 on 1 November 2026: product, correction\n- +0.1 on 27 October 2026: checklist\n- -0.3 on 8 October 2026: checklist\n\n### Truto Unified Calendar API\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Nylas Calendar and Scheduler API.** One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars, and since 6 October IAM keys can limit an agent to one calendar grant with chosen permissions. Event writes take no idempotency key, and the MCP's confirmation step covers email sends, not event changes or deletions.\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### Nylas Calendar and Scheduler API\n\n1. Address calendar calls to /v3/grants/\u003cgrant_id\u003e, one grant per connected account\n2. Use an IAM API key bound to the one grant the agent needs rather than the application key\n3. List events in the window before retrying a create, since event writes have no idempotency key\n4. Keep availability requests within 732 days, the cap since 10 October 2026\n5. On 429, use the passed-through `Retry-After` if present, otherwise back off per grant\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, Nylas Calendar and Scheduler API or Truto Unified Calendar API?\n\nNylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against Truto Unified Calendar API's 60.4 (C), and leads in 5 of 7 scored categories. Truto Unified Calendar API leads on reliability.\n\n### Do Nylas Calendar and Scheduler API and Truto Unified Calendar API need an API key?\n\nNylas Calendar and Scheduler API takes an API key or an OAuth sign-in. Truto Unified Calendar API needs an API key.\n\n### Can an agent call Nylas Calendar and Scheduler API and Truto Unified Calendar API without installing anything?\n\nNylas Calendar and Scheduler API has a hosted endpoint at https://api.us.nylas.com/v3. 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/nylas-calendar-vs-truto-calendar.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nylas-calendar-vs-truto-calendar.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"nylas-calendar\", \"b\": \"truto-calendar\"}`. From a terminal: `anchor compare nylas-calendar truto-calendar`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nylas-calendar.json and https://www.anchorterminal.com/api/v1/tools/truto-calendar.json\n\n## Other comparisons with Nylas Calendar and Scheduler API or Truto Unified Calendar API\n\n- [Acuity Scheduling API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar.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 Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/agenda-hero-vs-nylas-calendar.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 Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/apiroc-vs-nylas-calendar.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 Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar.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 Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cal-com-vs-nylas-calendar.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 Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar.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 Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cozi-vs-nylas-calendar.md)\n- [Cozi Family Organizer vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/cozi-vs-truto-calendar.md)\n- [Cronofy API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cronofy-vs-nylas-calendar.md)\n- [Cronofy API vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/cronofy-vs-truto-calendar.md)\n- [Google Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/google-calendar-api-vs-nylas-calendar.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 Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-nylas-calendar.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 Reclaim.ai](https://www.anchorterminal.com/compare/nylas-calendar-vs-reclaim-ai.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 Zoom Scheduler API](https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler.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- [Nylas Calendar and Scheduler API vs YouCanBookMe API](https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.md)\n- [SavvyCal API + MCP vs Truto Unified Calendar API](https://www.anchorterminal.com/compare/savvycal-vs-truto-calendar.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": "Nylas Calendar and Scheduler API vs Truto Unified Calendar API", "url": "" } ], "description": "Nylas Calendar and Scheduler scores 75.5 (BB) to Truto Unified Calendar's 60.4 (C) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Nylas Calendar and Scheduler API BB 75.5", "Truto Unified Calendar API C 60.4", "scores" ], "h1": "Nylas Calendar and Scheduler API vs Truto Unified Calendar API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/nylas-calendar-vs-truto-calendar", "published": "2026-10-01", "section": "tools", "title": "Nylas Calendar and Scheduler vs Truto Unified Calendar (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-truto-calendar" }, "tokens": { "markdown": 5350, "slim": 3130 }, "version": 1 }