{ "data": { "a": { "slug": "aurinko-calendar", "name": "Aurinko Calendar API", "vendor": "Yoxel, Inc.", "vendorUrl": "https://www.aurinko.io", "kind": "http-api", "category": "scheduling", "summary": "Unified calendar REST API from Yoxel, Inc. It reads and writes calendars and events on Google, Office 365, Outlook.com, Exchange and iCloud through one interface, with free/busy queries, booking profiles and webhooks.", "url": "https://www.anchorterminal.com/tools/aurinko-calendar", "markdownUrl": "https://www.anchorterminal.com/tools/aurinko-calendar.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/aurinko-calendar.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/aurinko-calendar.json", "license": "Proprietary service under Yoxel's Terms of Services Agreement", "transports": [ "http" ], "remoteUrl": "https://api.aurinko.io", "packages": [], "auth": "oauth", "authNotes": "Self-serve. A developer signs up at app.aurinko.io and gets a client ID and secret for each application. Each end user connects a calendar through Aurinko's OAuth flow at `/v1/auth/authorize`, which returns an account access token sent as a Bearer token. Eleven scopes include `Calendar.Read` and `Calendar.ReadWrite`. Group booking and other application-level calls take the client ID and secret as Basic auth. Production use with Google or Office 365 needs the developer's own OAuth app registration with those providers.", "pricing": "paid", "pricingNotes": "$1 an active account a month for one of Calendar, Contacts or Tasks with up to 1 GB of traffic, $1.50 for Email or CRM, and $2 for any number of APIs with unlimited traffic, per the billing FAQ. A 14-day trial needs no card, and API requests are blocked when it ends without a subscription (https://docs.aurinko.io/faq/how-does-aurinko-billing-work).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI spec or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.aurinko.io/", "llmsTxt": "https://docs.aurinko.io/llms.txt", "openapi": "https://apirefs.aurinko.io/assets/swagger.json", "capabilities": [ "calendar.read", "calendar.write", "calendar.availability", "calendar.booking", "calendar.webhooks" ], "tags": [ "hosted", "oauth", "openapi", "llms-txt", "webhooks", "closed-source", "free-trial" ], "graded": true, "anchor": { "graded": true, "score": 45.6, "grade": "E", "agentReady": false, "rank": 654, "ranked": true, "rankOf": 722, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 20, "payments": 40, "reliability": 40, "schema": 66, "security": 41, "transparency": 44 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A public OpenAPI 3.0 spec covers 154 operations, with free/busy, meeting-time suggestion and booking profiles alongside calendar reads and writes, and prices start at $1 an active account a month. No status page, SLA, changelog or official SDK was found, and the application's client secret reaches every connected account.", "bestFor": "A product that connects many users' Google and Microsoft calendars and wants availability and booking at a low price per account.", "strengths": [ "Public OpenAPI 3.0 spec at `apirefs.aurinko.io/assets/swagger.json` with 154 operations, 110 of them carrying a cURL sample", "Availability in three forms, `/v1/calendars/freeBusy`, `/v1/calendars/suggestMeetingTimes` and booking profiles for one calendar or a group", "Prices published per active account a month ($1, $1.50 and $2), with a 14-day trial that needs no card", "Eleven OAuth scopes, with `Calendar.Read` separate from `Calendar.ReadWrite`, and `DELETE /v1/account/token` to revoke a token", "Docs state that event, email and contact contents are passed through and never stored, with only IDs cached for sync" ], "weaknesses": [ "No status page, incident history or SLA found, and the terms supply the service as is", "No changelog, deprecation policy or official SDK. The only npm package, `aurinko-sdk`, is unofficial", "The application's client ID and secret, sent as Basic auth with `X-Aurinko-Account-Id`, reach every connected account", "SOC 2 is not yet held. The security statement of 18 June 2026 targets a Type I examination for Q3 2026", "Terms and privacy policy date from 11 August 2022, with no retention period, DPA or sub-processor list found" ], "agentNotes": [ "Use `https://api.aurinko.io/v1`. Several cURL examples in the docs print `https:/api.aurinko.io` with one slash", "Send `If-Match` with the event's `etag` on `PATCH /v1/calendars/{calendarId}/events/{eventId}`. A stale value returns 412", "Use `primary` as the calendar ID for an account's main calendar, and page with `pageToken` until none is returned", "Hold a slot with `reserveForMinutes` on the booking `meeting` call, then confirm or cancel the reservation, since no idempotency key exists", "Retry 429, 408 and 5xx with exponential backoff. Do not retry 404. A 429 can come from Google or Microsoft limits behind the API" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.6 } ], "editorialScores": { "ergonomics": 56, "maintenance": 20, "payments": 40, "reliability": 40, "schema": 66, "security": 41, "transparency": 27 }, "provenanceScore": 60 }, "connect": { "http": "curl -H 'Authorization: Bearer \u003caccess_token\u003e' \\\n -X GET https://api.aurinko.io/v1/calendars/primary" }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/aurinko-calendar" }, "area": "everyday", "unitPrices": [ { "item": "Unified API, one of Calendar, Contacts or Tasks", "unit": "account-month", "usd": 1, "note": "Per active account, up to 1 GB of traffic a month" }, { "item": "Email or CRM", "unit": "account-month", "usd": 1.5, "note": "Per active account, up to 1 GB of traffic a month" }, { "item": "Full platform, any number of APIs", "unit": "account-month", "usd": 2, "note": "Per active account, unlimited traffic" } ], "provenance": { "legalEntity": "Yoxel, Inc.", "domain": "aurinko.io", "domainRegistered": "2019-05-08", "endpointOnVendorDomain": true, "terms": "https://www.aurinko.io/terms/", "privacy": "https://www.aurinko.io/privacy/", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Terms of Services Agreement, last updated 11 August 2022, names Yoxel, Inc., organised under the laws of California, and covers the API and the workspace integrations platform. Disputes go to binding arbitration.", "The privacy policy, last updated 11 August 2022, covers the site and the services, API included, and commits to Google's API Services User Data Policy and its Limited Use requirements.", "The API answers at api.aurinko.io, the portal at app.aurinko.io and the reference at apirefs.aurinko.io, all on the vendor's domain.", "www.aurinko.io/.well-known/security.txt returns 404. The security statement gives security@yoxel.com for reports.", "No status page or changelog is linked from the site, the docs or the spec. status.aurinko.io did not resolve from our network.", "RDAP for aurinko.io gives a registration date of 2019-05-08." ], "score": 60 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/aurinko-calendar.json", "live": { "slug": "aurinko-calendar", "probe": { "target": "https://api.aurinko.io", "method": "get", "lastAt": "2026-10-08T21:12:04.565033941Z", "lastOk": true, "lastStatus": 404, "lastMs": 255, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 256, "p95ms24h": 311, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "updatedAt": "2026-10-08T21:12:04.565033941Z" } }, "answer": "Nylas Calendar and Scheduler API scores 71 (BB) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories.", "b": { "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", "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 as a Bearer token. 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 the same API 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 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 with 25 email and calendar accounts ($2.00 each after), 35 calendar-only accounts ($1.50 each after), 70 Notetaker hours then $0.70 an hour, and 50 Agent Accounts then $0.40 each. Enterprise is custom with volume bands, a HIPAA BAA and an uptime SLA (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-09-30", "graded": true, "anchor": { "graded": true, "score": 71, "grade": "BB", "agentReady": true, "rank": 121, "ranked": true, "rankOf": 722, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 88, "payments": 40, "reliability": 75, "schema": 91, "security": 59, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars. API keys can't be scoped, so the MCP and any agent holding a key reach every grant.", "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", "Free plan with 5 connected accounts and no card", "MCP docs warn about hidden instructions in calendar events and email, and sends need a confirmation call", "API keys with an expiry, rotated and revoked through the admin API", "Dated changelog with 20 entries between 20 August and 28 September 2026" ], "weaknesses": [ "API keys can't be scoped, so the MCP and any agent holding a key reach every grant", "No idempotency key on event writes, only on email send", "Several status incidents since July on email, IMAP and webhooks, including about six hours on 10 September", "Extra connected accounts cost $1.50 to $2.25 a month each", "No security.txt on nylas.com" ], "agentNotes": [ "Address calendar calls to /v3/grants/\u003cgrant_id\u003e, one grant per connected account", "List events in the window before retrying a create, since event writes have no idempotency key", "Point the MCP client at mcp.eu.nylas.com if the application lives in the EU region", "On 429, use the passed-through `Retry-After` if present, otherwise back off per grant", "Mint a short-lived API key for the agent with `expires_in` rather than sharing the main one" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71 } ], "editorialScores": { "ergonomics": 71, "maintenance": 88, "payments": 40, "reliability": 75, "schema": 91, "security": 59, "transparency": 67 }, "provenanceScore": 85 }, "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-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 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": "none", "checked": "2026-09-30", "notes": [ "The terms (updated 23 June 2025) name Nylas, Inc. in Palo Alto, California, under California law with arbitration.", "www.nylas.com/.well-known/security.txt returns 404.", "The status page for the v3 API is status-v3.nylas.com." ], "score": 85 }, "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-10-08T21:12:17.129244781Z", "lastOk": true, "lastStatus": 404, "lastMs": 158, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 156, "p95ms24h": 218, "samples24h": 271, "samples30d": 1955, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://status-v3.nylas.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:13.244904137Z" }, "versions": [ { "registry": "github", "name": "nylas/nylas-nodejs", "version": "v8.4.0", "released": "2026-06-24", "seenAt": "2026-10-08T16:22:55.312865756Z" }, { "registry": "npm", "name": "nylas", "version": "8.4.0", "seenAt": "2026-10-08T16:22:54.308947086Z" }, { "registry": "pypi", "name": "nylas", "version": "6.18.0", "released": "2026-09-30", "seenAt": "2026-10-08T16:22:55.123440605Z" } ], "githubStars": 181, "npmWeekly": 289344, "pypiWeekly": 90308, "securityTxt": { "url": "https://nylas.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:57.948763904Z" }, "llmsTxt": { "url": "https://developer.nylas.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:42.408305249Z" }, "domain": { "domain": "nylas.com", "registered": "2001-11-07", "source": "https://rdap.verisign.com/com/v1/domain/nylas.com", "checkedAt": "2026-10-04T13:09:31.916917182Z" }, "pages": [ { "url": "https://developer.nylas.com/docs/changelogs/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:15.583829343Z", "changedAt": "2026-10-07T18:04:05.758316402Z", "fingerprint": "458975a828b6" }, { "url": "https://www.nylas.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:29:27.452233211Z", "changedAt": "2026-10-08T18:29:27.452233211Z", "fingerprint": "30c4c5a49b00" }, { "url": "https://www.nylas.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:29:29.467660184Z", "changedAt": "2026-10-07T18:13:12.88812361Z", "fingerprint": "f4ee5c9c3c1c" }, { "url": "https://www.nylas.com/legal/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:29:25.388256284Z", "changedAt": "2026-10-07T18:13:08.475272084Z", "fingerprint": "fa78a0e10b5e" } ], "updatedAt": "2026-10-08T21:12:17.129244781Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Yoxel, Inc.", "b": "Nylas", "name": "Vendor" }, { "a": "https://api.aurinko.io", "b": "https://api.us.nylas.com/v3", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Yoxel's Terms of Services Agreement", "b": "MIT (SDKs)", "name": "Licence" }, { "a": "none", "b": "38", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-09-30", "name": "Last release" }, { "a": "2022-08-11", "b": "2025-06-23", "name": "Terms last updated" }, { "a": "2022-08-11", "b": "2026-01-06", "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": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "181 stars, 281k npm/wk, 104k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Nylas Calendar and Scheduler API scores 71 (BB) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Aurinko Calendar API or Nylas Calendar and Scheduler API?" }, { "answer": "Aurinko Calendar API uses an OAuth sign-in. Nylas Calendar and Scheduler API takes an API key or an OAuth sign-in.", "question": "Do Aurinko Calendar API and Nylas Calendar and Scheduler API need an API key?" }, { "answer": "Yes. Aurinko Calendar API has a hosted endpoint at https://api.aurinko.io and Nylas Calendar and Scheduler API at https://api.us.nylas.com/v3.", "question": "Can an agent call Aurinko Calendar API and Nylas Calendar and Scheduler API without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "A product that connects many users' Google and Microsoft calendars and wants availability and booking at a low price per account.", "slug": "aurinko-calendar", "watchFor": "No status page, incident history or SLA found, and the terms supply the service as is" }, { "aheadOn": [ "Reliability, 75 against 40", "Schema \u0026 documentation, 91 against 66", "Agent ergonomics, 71 against 56", "Security \u0026 auth, 59 against 41", "Maintenance \u0026 community, 88 against 20", "Transparency \u0026 trust, 76 against 44" ], "also": [ "Agent-ready, a grade of BB or better", "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": "API keys can't be scoped, so the MCP and any agent holding a key reach every grant" } ], "job": { "capability": "calendar.read", "name": "Calendar read" }, "others": [ { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar.json", "title": "Acuity Scheduling API vs Aurinko Calendar API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar" }, { "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/apiroc-vs-aurinko-calendar.json", "title": "Apiroc Unified Calendar API vs Aurinko Calendar API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-aurinko-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/aurinko-calendar-vs-cal-com.json", "title": "Aurinko Calendar API vs Cal.com API v2 + MCP", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cal-com" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.json", "title": "Aurinko Calendar API vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy.json", "title": "Aurinko Calendar API vs Cronofy API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-google-calendar-api.json", "title": "Aurinko Calendar API vs Google Calendar API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-google-calendar-api" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-microsoft-graph-calendar.json", "title": "Aurinko Calendar API vs Microsoft Graph Calendar API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-microsoft-graph-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/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/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/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/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" } ], "scores": [ { "aurinko-calendar": 40, "by": 35, "edge": "nylas-calendar", "key": "reliability", "name": "Reliability", "nylas-calendar": 75, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aurinko-calendar": 66, "by": 25, "edge": "nylas-calendar", "key": "schema", "name": "Schema \u0026 documentation", "nylas-calendar": 91, "weight": 13 }, { "aurinko-calendar": 56, "by": 15, "edge": "nylas-calendar", "key": "ergonomics", "name": "Agent ergonomics", "nylas-calendar": 71, "weight": 13 }, { "aurinko-calendar": 41, "by": 18, "edge": "nylas-calendar", "key": "security", "name": "Security \u0026 auth", "nylas-calendar": 59, "weight": 14 }, { "aurinko-calendar": 40, "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "nylas-calendar": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "aurinko-calendar": 20, "by": 68, "edge": "nylas-calendar", "key": "maintenance", "name": "Maintenance \u0026 community", "nylas-calendar": 88, "weight": 7 }, { "aurinko-calendar": 44, "by": 32, "edge": "nylas-calendar", "key": "transparency", "name": "Transparency \u0026 trust", "nylas-calendar": 76, "weight": 7 } ], "summary": "Nylas Calendar and Scheduler API scores 71 (BB) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Both do calendar read.", "verdicts": { "aurinko-calendar": "A public OpenAPI 3.0 spec covers 154 operations, with free/busy, meeting-time suggestion and booking profiles alongside calendar reads and writes, and prices start at $1 an active account a month. No status page, SLA, changelog or official SDK was found, and the application's client secret reaches every connected account.", "nylas-calendar": "One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars. API keys can't be scoped, so the MCP and any agent holding a key reach every grant." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar", "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar.md", "slim": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar.min.md" }, "markdown": "Nylas Calendar and Scheduler API scores 71 (BB) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Both do calendar read.\n\n- Aurinko Calendar API: grade E, 45.6/100, rank #654 of 722. Markdown https://www.anchorterminal.com/tools/aurinko-calendar.md · JSON https://www.anchorterminal.com/api/v1/tools/aurinko-calendar.json\n- Nylas Calendar and Scheduler API: grade BB, 71/100, rank #121 of 722. Markdown https://www.anchorterminal.com/tools/nylas-calendar.md · JSON https://www.anchorterminal.com/api/v1/tools/nylas-calendar.json\n\n## Which one, for what\n\n### Aurinko Calendar API (E)\n\nGood for: A product that connects many users' Google and Microsoft calendars and wants availability and booking at a low price per account.\n\nWatch for: No status page, incident history or SLA found, and the terms supply the service as is\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- Reliability, 75 against 40\n- Schema \u0026 documentation, 91 against 66\n- Agent ergonomics, 71 against 56\n- Security \u0026 auth, 59 against 41\n- Maintenance \u0026 community, 88 against 20\n- Transparency \u0026 trust, 76 against 44\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Free to start without a card\n\nWatch for: API keys can't be scoped, so the MCP and any agent holding a key reach every grant\n\n\n## Score by category\n\n| Category | Weight | Aurinko Calendar API | Nylas Calendar and Scheduler API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 75 | Nylas Calendar and Scheduler API +35 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 91 | Nylas Calendar and Scheduler API +25 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 71 | Nylas Calendar and Scheduler API +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 59 | Nylas Calendar and Scheduler API +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 88 | Nylas Calendar and Scheduler API +68 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 44 | 76 | Nylas Calendar and Scheduler API +32 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.6 · E** | **71 · BB** | |\n\n## Facts side by side\n\n| Fact | Aurinko Calendar API | Nylas Calendar and Scheduler API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Yoxel, Inc. | Nylas |\n| Hosted endpoint | `https://api.aurinko.io` | `https://api.us.nylas.com/v3` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Yoxel's Terms of Services Agreement | MIT (SDKs) |\n| Tools exposed | none | 38 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-09-30 |\n| Terms last updated | 2022-08-11 | 2025-06-23 |\n| Privacy policy last updated | 2022-08-11 | 2026-01-06 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | none | 181 stars, 281k npm/wk, 104k PyPI/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## Verdicts\n\n**Aurinko Calendar API.** A public OpenAPI 3.0 spec covers 154 operations, with free/busy, meeting-time suggestion and booking profiles alongside calendar reads and writes, and prices start at $1 an active account a month. No status page, SLA, changelog or official SDK was found, and the application's client secret reaches every connected account.\n\n**Nylas Calendar and Scheduler API.** One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars. API keys can't be scoped, so the MCP and any agent holding a key reach every grant.\n\n## Before you call either\n\n### Aurinko Calendar API\n\n1. Use `https://api.aurinko.io/v1`. Several cURL examples in the docs print `https:/api.aurinko.io` with one slash\n2. Send `If-Match` with the event's `etag` on `PATCH /v1/calendars/{calendarId}/events/{eventId}`. A stale value returns 412\n3. Use `primary` as the calendar ID for an account's main calendar, and page with `pageToken` until none is returned\n4. Hold a slot with `reserveForMinutes` on the booking `meeting` call, then confirm or cancel the reservation, since no idempotency key exists\n5. Retry 429, 408 and 5xx with exponential backoff. Do not retry 404. A 429 can come from Google or Microsoft limits behind the API\n\n### Nylas Calendar and Scheduler API\n\n1. Address calendar calls to /v3/grants/\u003cgrant_id\u003e, one grant per connected account\n2. List events in the window before retrying a create, since event writes have no idempotency key\n3. Point the MCP client at mcp.eu.nylas.com if the application lives in the EU region\n4. On 429, use the passed-through `Retry-After` if present, otherwise back off per grant\n5. Mint a short-lived API key for the agent with `expires_in` rather than sharing the main one\n\n## Questions\n\n### Which is better for AI agents, Aurinko Calendar API or Nylas Calendar and Scheduler API?\n\nNylas Calendar and Scheduler API scores 71 (BB) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories.\n\n### Do Aurinko Calendar API and Nylas Calendar and Scheduler API need an API key?\n\nAurinko Calendar API uses an OAuth sign-in. Nylas Calendar and Scheduler API takes an API key or an OAuth sign-in.\n\n### Can an agent call Aurinko Calendar API and Nylas Calendar and Scheduler API without installing anything?\n\nYes. Aurinko Calendar API has a hosted endpoint at https://api.aurinko.io and Nylas Calendar and Scheduler API at https://api.us.nylas.com/v3.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aurinko-calendar\", \"b\": \"nylas-calendar\"}`. From a terminal: `anchor compare aurinko-calendar nylas-calendar`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/aurinko-calendar.json and https://www.anchorterminal.com/api/v1/tools/nylas-calendar.json\n\n## Other comparisons with Aurinko Calendar API or Nylas Calendar and Scheduler API\n\n- [Acuity Scheduling API vs Aurinko Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar.md)\n- [Acuity Scheduling API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar.md)\n- [Apiroc Unified Calendar API vs Aurinko Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-aurinko-calendar.md)\n- [Apiroc Unified Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/apiroc-vs-nylas-calendar.md)\n- [Aurinko Calendar API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-cal-com.md)\n- [Aurinko Calendar API vs Calendly API + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.md)\n- [Aurinko Calendar API vs Cronofy API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy.md)\n- [Aurinko Calendar API vs Google Calendar API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-google-calendar-api.md)\n- [Aurinko Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-microsoft-graph-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- [Calendly API + MCP vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar.md)\n- [Cronofy API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cronofy-vs-nylas-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- [Microsoft Graph Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-nylas-calendar.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Aurinko Calendar API vs Nylas Calendar and Scheduler API", "url": "" } ], "description": "Nylas Calendar and Scheduler API scores 71 (BB) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Both do calendar read. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Aurinko Calendar API E 45.6", "Nylas Calendar and Scheduler API BB 71", "scores" ], "h1": "Aurinko Calendar API vs Nylas Calendar and Scheduler API", "image": "https://www.anchorterminal.com/assets/og/compare-aurinko-calendar-vs-nylas-calendar.png", "path": "/compare/aurinko-calendar-vs-nylas-calendar", "published": "2026-10-01", "section": "tools", "title": "Aurinko Calendar API vs Nylas Calendar and Scheduler API for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar" }, "tokens": { "markdown": 2300, "slim": 680 }, "version": 1 }