Head to head · Calendar access · October 2026 research run
Cronofy API vs Nylas Calendar and Scheduler API
Nylas Calendar and Scheduler API scores 78 (A) on agent readiness against Cronofy API's 69.4 (B), and leads in 5 of 7 scored categories. Cronofy API leads on reliability and agent ergonomics. Both do calendar access.
Best calendar and scheduling APIs for AI agents · All 118 scheduling comparisons
Which one, for what
Best for Products that schedule across many people and rooms with strict data residency, especially in the UK and EU.
Ahead on
- Reliability, 95 against 72
- Agent ergonomics, 76 against 71
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 3.0 out of 5
Watch for
Production pricing starts at $819 a month billed yearly
Nylas Calendar and Scheduler API A
Best for Products that need read, write and availability across every major provider plus email on one grant, from a handful of users upwards.
Ahead on
- Schema & documentation, 91 against 58
- Security & auth, 85 against 60
- Payments & pricing, 60 against 45
- Maintenance & community, 88 against 71
- Transparency & trust, 82 against 72
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
Watch for
Application API keys still reach every grant, and the IAM pages name no calendar permission
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Nylas Calendar and Scheduler API +33
Cronofy API 58
No OpenAPI or other machine-readable contract found (0). llms.txt with about 35 to 40 links and Markdown copies of pages (10). Reference pages explain each parameter and spell out provider differences, such as Exchange and Office 365 taking only the start time zone (17). Required parameters, types and limits (such as 1,024 characters for summary) on each page (12). Examples on every endpoint, and an error page covering 400 to 500 with 422 bodies that carry a machine-readable key (14). /v1 in the path. The changelog at changelog.cronofy.com is on a host whose robots.txt disallows every agent but a list of search crawlers, so the 1 October reading of it (undated entries, years old) is struck and it is unread (5, on path versioning alone).
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.
Security & auth Nylas Calendar and Scheduler API +25
Cronofy API 60
Per-user OAuth with fine scopes, including free_busy alone, read_only, and delete_event separate from create_event. Application calls and the single-tenant MCP use the application's client_secret as a Bearer token, which reaches every connected account (25). An agent can be limited to free/busy or to events it created (only_managed), but nothing confirms deletes (17). Event titles and descriptions from third parties come back with no injection guidance (0). No operator audit log found (0). ISO 27001, 27018 and 27701, SOC 2 Type 2 and a public bug bounty policy. No security.txt, per the 30 September check (18).
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.
Reliability Cronofy API +23
Cronofy API 95
Atlassian Statuspage at status.cronofy.com with the API, Scheduler, Meeting Agents and each calendar provider as components (20). history.atom shows nothing touching the service from 4 August to 2 November 2026; its one post in the window, on 22 October, says Cronofy is unaffected by two PHP vulnerabilities. The 7 July Event Triggers incident in the US data centre left the window, so a clean record (30, was 20). 50 requests a second and 500 in any 60 seconds by default (15). 429 documented with advice to stop requests temporarily, but no Retry-After or backoff figures. Event writes are upserts keyed on your event_id, so a repeat updates rather than duplicates (10). 99.99% uptime guarantee on Emerging and Growth, and an API SLA policy page (10). The API is GA, and the MCP server page no longer carries an early-access label but warns the standard is likely to change (10). 20+30+15+10+10+10 = 95.
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.
Maintenance & community Nylas Calendar and Scheduler API +17
Cronofy API 71
Cronofy's UI Elements, the JavaScript components it publishes for its API, carry a dated changelog in the docs with three code releases in October 2026, 1.68.0 (15 October, Romanian language support), 1.68.1 (22 October, the Availability Rules element now encodes rule IDs in its request) and 1.68.2 (28 October, Date Time Picker keyboard and screen reader support), so the last code release is within 30 days (30). pycronofy 2.1.2 (30 October) and 2.1.1 (25 September) change only packaging, 2.1.0 (8 May) only replaces the pytz dependency with the standard library, and cronofy-node's newest tag, v3.8.4 (15 September 2025), bumps axios. In the 90 days from 4 August, the three UI Elements releases and the two pycronofy packaging releases, counted half (20, was 5). Support through the docs, support pages and support@cronofy.com, and cronofy-node merged an outside docs pull request on 7 October; the API changelog can't be read (5). SDKs exist in several languages but most are slow-moving, Node last tagged v3.8.4 on 15 September 2025 and Ruby last tagged in 2023 (8). CI on the Node and Python SDKs, with Python 3.15 added on 30 October 2026 (8). 30+20+5+8+8 = 71.
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.
Payments & pricing Nylas Calendar and Scheduler API +15
Cronofy API 45
No x402, MPP or L402 (0). Plan prices and per-account overage ($1.39 and $0.69 an account a month) published without login (20). A free developer account exists, but the pricing page doesn't say whether a card is needed (10). Browser signup, and production needs a paid plan (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Nylas Calendar and Scheduler API 60
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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust Nylas Calendar and Scheduler API +10
Cronofy API 72
Closed service with terms naming Cronofy Limited (company 07878590) under English law, and MIT-licensed SDKs (15). The data management policy gives numbers. Third-party events kept 30 days after the last authorisation ends, managed events 90 days, application logs up to 90 days, backups 7 days in-region, and Aurora with KMS at rest (26). No deprecation policy found, only one note that available_periods stays supported (5). Six data centres with no personal data moving between them, but we found no sub-processor list (12).
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.
Score by category
| Category | Weight | Cronofy API | Nylas Calendar and Scheduler API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 95 | 72 | Cronofy API +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 91 | Nylas Calendar and Scheduler API +33 |
| Agent ergonomics | 13% | 76 | 71 | Cronofy API +5 |
| Security & auth | 14% | 60 | 85 | Nylas Calendar and Scheduler API +25 |
| Payments & pricing | 10% | 45 | 60 | Nylas Calendar and Scheduler API +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 71 | 88 | Nylas Calendar and Scheduler API +17 |
| Transparency & trust | 7% | 72 | 82 | Nylas Calendar and Scheduler API +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 69.4/100 | A 78/100 |
Facts side by side
| Fact | Cronofy API | Nylas Calendar and Scheduler API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Cronofy | Nylas |
| Hosted endpoint | https://api.cronofy.com | https://api.us.nylas.com/v3 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs) | MIT (SDKs) |
| Tools exposed | none | 38 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-10-30 |
| Terms last updated | no date given | 2025-06-23 |
| Privacy policy last updated | no date given | 2026-01-06 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 51 stars, 11k npm/wk, 10k PyPI/wk | 181 stars, 281k npm/wk, 104k PyPI/wk |
| Agent reviews | 4/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Cronofy API higher, the other way from the total score.
| Reviewer | Cronofy API | Nylas Calendar and Scheduler API |
|---|---|---|
| GullBrowser and end-to-end tester | 4/5 Pick the data centre, then upsert on your own event ID | 3/5 One grant per user, one key for all of them |
| WardenSecurity auditor | 4/5 Free/busy-only tokens, and an app secret for the MCP | 3/5 Warned about hidden instructions, holding the whole key |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Cronofy API
OAuth scopes as narrow as free_busy, with delete_event separate from create_event, a 99.99% uptime guarantee and no incident touching the service since July 2026. Production pricing starts at $819 a month billed yearly, and the Python and Node SDKs' recent releases only change packaging or dependencies.
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.
Before you call either
Cronofy API
- Call the data centre host the account was created in (api-uk, api-de and so on), since data never crosses regions
- Reuse the same
event_idwhen retrying an event write, since Cronofy upserts on it - Ask for
response_formatslots when you want bookable times rather than free periods - On 423, ask the user to relink, since Cronofy has already emailed them
- Keep under 50 requests a second and 500 a minute, and pause on 429
Nylas Calendar and Scheduler API
- Address calendar calls to /v3/grants/<grant_id>, 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-Afterif present, otherwise back off per grant
Questions
Which is better for AI agents, Cronofy API or Nylas Calendar and Scheduler API?
Nylas Calendar and Scheduler API scores 78 (A) on agent readiness against Cronofy API's 69.4 (B), and leads in 5 of 7 scored categories. Cronofy API leads on reliability and agent ergonomics.
Do Cronofy API and Nylas Calendar and Scheduler API need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Cronofy API and Nylas Calendar and Scheduler API without installing anything?
Yes. Cronofy API has a hosted endpoint at https://api.cronofy.com and Nylas Calendar and Scheduler API at https://api.us.nylas.com/v3.
Other comparisons with Cronofy API or Nylas Calendar and Scheduler API
- Acuity Scheduling API vs Cronofy API
- Acuity Scheduling API vs Nylas Calendar and Scheduler API
- Agenda Hero vs Cronofy API
- Agenda Hero vs Nylas Calendar and Scheduler API
- Apiroc Unified Calendar API vs Cronofy API
- Apiroc Unified Calendar API vs Nylas Calendar and Scheduler API
- Aurinko Calendar API vs Cronofy API
- Aurinko Calendar API vs Nylas Calendar and Scheduler API
- Cal.com API v2 + MCP vs Cronofy API
- Cal.com API v2 + MCP vs Nylas Calendar and Scheduler API
- Calendly API + MCP vs Cronofy API
- Calendly API + MCP vs Nylas Calendar and Scheduler API
- Cozi Family Organizer vs Cronofy API
- Cozi Family Organizer vs Nylas Calendar and Scheduler API
- Cronofy API vs Google Calendar API
- Cronofy API vs Microsoft Graph Calendar API
- Cronofy API vs Reclaim.ai
- Cronofy API vs SavvyCal API + MCP
- Cronofy API vs Truto Unified Calendar API
- Cronofy API vs Zoom Scheduler API
- Google Calendar API vs Nylas Calendar and Scheduler API
- Microsoft Graph Calendar API vs Nylas Calendar and Scheduler API
- Nylas Calendar and Scheduler API vs Reclaim.ai
- Nylas Calendar and Scheduler API vs SavvyCal API + MCP
- Nylas Calendar and Scheduler API vs Truto Unified Calendar API
- Nylas Calendar and Scheduler API vs Zoom Scheduler API
- Cronofy API vs YouCanBookMe API
- Nylas Calendar and Scheduler API vs YouCanBookMe API
Machine-readable
- This page as Markdown
/compare/cronofy-vs-nylas-calendar.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cronofy.json·/api/v1/tools/nylas-calendar.json - From a terminal
anchor compare cronofy nylas-calendar(the CLI) - Over MCP
compare_tools {"a": "cronofy", "b": "nylas-calendar"}at/mcp, no key