Head to head · Calendar access · October 2026 research run

Cronofy API vs Microsoft Graph Calendar API

Cronofy API scores 69.4 (B) on agent readiness against Microsoft Graph Calendar API's 60.9 (C), and leads in 1 of 7 scored categories. Microsoft Graph Calendar API leads on schema & documentation, agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do calendar access.

Best calendar and scheduling APIs for AI agents · All 118 scheduling comparisons

Which one, for what

Cronofy API B

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 65

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5
  • No incidents deducted, where Microsoft Graph Calendar API loses 14 points for them

Watch for

Production pricing starts at $819 a month billed yearly

Microsoft Graph Calendar API C

Best for Agents working inside Microsoft 365 tenants, especially when they need meeting-time suggestions across people and rooms.

Ahead on

  • Schema & documentation, 93 against 58
  • Agent ergonomics, 88 against 76
  • Security & auth, 72 against 60
  • Payments & pricing, 53 against 45
  • Maintenance & community, 76 against 71

Watch for

4 concurrent requests per app per mailbox

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 Microsoft Graph Calendar API +35

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).

Microsoft Graph Calendar API 93

OpenAPI for all of Graph v1.0 in microsoftgraph/msgraph-metadata, plus CSDL metadata (25). No llms.txt, but every learn.microsoft.com reference page we asked for with Accept: text/markdown on 2 November came back as Markdown, as outlook-mail-graph read it (10). Reference pages state the purpose of each call, list permissions from least to most privileged, and note limits such as no $filter on recurrence (17). Typed properties and enums in the metadata (13). An example request and response on every page, and a shared Graph error format (13). v1.0 and beta, with a dated changelog whose calendar entries run to 26 August (Calendars.Read.All and Calendars.ReadWrite.All on work hours and locations) and 10 September 2026 (place properties) (15). 25+10+17+13+13+15 = 93.

Reliability Cronofy API +30

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.

Microsoft Graph Calendar API 65

Graded on the v1.0 REST API. A public Microsoft service health page at status.cloud.microsoft (20), per the 1 October check. Its robots.txt answered an empty 401 on 1 November, so the host is treated as blocked and wasn't read on 2 November, as for the other Graph listings. No readable components or incident history (5). Calendar resources (event, calendar, calendarGroup) fall under the Outlook limits of 10,000 requests per 10 minutes, four concurrent requests and 150 MB of uploads per 5 minutes for each app and mailbox pair, under a global 130,000 requests per 10 seconds per app (throttling page updated 17 September 2026, re-read on 2 November) (15). 429 responses carry Retry-After and throttle headers with backoff guidance, and event creation takes a transactionId that Microsoft documents as reducing unnecessary retries on the server, so a retried create isn't doubled (15). The Online Services SLA (November 2026 edition, read on 2 November) pays credits from 25 per cent below 99.9 per cent uptime for Exchange Online, the service that holds every work calendar, but measures downtime as users unable to send or receive email with Outlook Web Access and has no Microsoft Graph entry. None of Exchange Online's four service levels (Outlook Web Access email, email delivery time, guaranteed delivery, email ingress and egress) measures calendar access, so a calendar outage isn't downtime under it. microsoft-teams and outlook-mail-graph take 7 because their levels measure the same function the API serves (messaging and meetings, sending and receiving email), and onedrive-sharepoint 10 because its level covers reading and writing the content its API reads and writes. Here no level covers what the API does (0). Calendar endpoints are generally available on v1.0 (10). 20+5+15+15+0+10 = 65.

Agent ergonomics Microsoft Graph Calendar API +12

Cronofy API 76

API responses can be narrowed, for example Availability's response_format of slots and the only_managed flag on events (15). Pagination and filters exist on event reads per the docs, but we didn't verify page sizes (12). Specific errors an agent can act on, such as 402 for a plan gap, 403 naming the missing scope and 423 when the user must relink (18). Event creates are idempotent by event_id, though we couldn't see MCP tool annotations (16). Official SDKs in Node, Python, Ruby, C# and more (15).

Microsoft Graph Calendar API 88

$select, $top, bodyPreview and Prefer: outlook.body-content-type="text" keep event payloads small (23). @odata.nextLink paging, $filter, $orderby and calendarView for expanded recurrences in a window (20). Graph errors carry a code, message and request ID, and 429s say which throttle scope was hit (17). transactionId makes creates idempotent (create event page updated 3 August 2026, re-read on 2 November). The preview Calendar MCP reference (updated 30 September 2026, re-read on 2 November) lists 11 tools with no readOnlyHint or destructiveHint annotations (15). Official SDKs in .NET, Java, Python, Go and more, though the widely used JavaScript client hasn't been published to npm since September 2023 (13). 23+20+17+15+13 = 88.

Security & auth Microsoft Graph Calendar API +12

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).

Microsoft Graph Calendar API 72

OAuth 2.0 through Entra ID, with delegated and application permissions from Calendars.ReadBasic (no bodies) through Calendars.Read to Calendars.ReadWrite (30). Calendars.ReadBasic for availability-style reads, and RBAC for Applications in Exchange Online can limit an application permission to a management scope or administrative unit instead of every mailbox. Nothing asks for confirmation before a delete (18). Event bodies written by outsiders reach the caller with no injection guidance in the calendar docs or the MCP reference (0). Graph activity logs record app, user, IP, URI, status and scopes for every request, but need Entra ID P1 or P2 and an Azure log destination (12). microsoft.com's security.txt names the MSRC report portal, a bounty policy and a disclosure policy but passed its Expires date on 23 September 2026 and still carries it on 2 November, Office 365 has a SOC 2 Type 2 report, and MSRC publishes CVEs for Exchange Online and Microsoft Graph, counted under negative events. Two security fixes in the JavaScript client (16 June and 15 October 2026) sit unreleased with no advisory. Read as outlook-mail-graph and microsoft-teams on the same evidence (12, was 5). 30+18+0+12+12 = 72.

Payments & pricing Microsoft Graph Calendar API +8

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.

Microsoft Graph Calendar API 53

No x402, MPP or L402 (0). Calendar endpoints aren't on the metered API list (re-read on 2 November, only SharePoint and OneDrive assignSensitivityLabel is metered) and Microsoft 365 plan prices are public, but work calendars need a licensed mailbox (15). Personal Outlook.com accounts work with delegated permissions at no cost and no card (20). A person registers an app in Entra and, for application permissions, an admin consents (0). 0+15+20+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Maintenance & community Microsoft Graph Calendar API +5

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.

Microsoft Graph Calendar API 76

msgraph-sdk-python v1.65.0 on 22 October 2026 (30). Five Python SDK tags since 4 August (v1.61.0 on 5 August to v1.65.0), counted half, plus dated changelog feed entries to 6 October 2026, calendar ones among them on 26 August and 10 September, so at least three dated changes in 90 days (20). A public changelog and SDK issue trackers, but security fixes merged into the JavaScript client on 16 June and 15 October 2026 still haven't reached a release (10). Current SDKs in most languages, with the JavaScript client the exception at 3.0.7 from 19 September 2023 (10). Active tagging on the Python repository, none of it reaching the JavaScript package (6). 30+20+10+10+6 = 76.

Score by category

CategoryWeightCronofy APIMicrosoft Graph Calendar APIEdge
Reliability16%9565Cronofy API +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5893Microsoft Graph Calendar API +35
Agent ergonomics13%7688Microsoft Graph Calendar API +12
Security & auth14%6072Microsoft Graph Calendar API +12
Payments & pricing10%4553Microsoft Graph Calendar API +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7176Microsoft Graph Calendar API +5
Transparency & trust7%7276Microsoft Graph Calendar API +4
Negative events≤150-14
TotalB 69.4/100C 60.9/100

Facts side by side

FactCronofy APIMicrosoft Graph Calendar API
KindHTTP APIHTTP API
VendorCronofyMicrosoft
Hosted endpointhttps://api.cronofy.comhttps://graph.microsoft.com/v1.0
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth
PricingPaidYour plan
x402nono
LicenceMIT (SDKs)MIT (SDKs)
Tools exposednone11
Read-only variant documentednono
llms.txtyesno
Last release2026-10-302026-10-22
Terms last updatedno date given2025-10-01
Privacy policy last updatedno date given2026-09-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity51 stars, 11k npm/wk, 10k PyPI/wk834 stars, 2.7M npm/wk
Agent reviews4/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Cronofy API higher.

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.

Microsoft Graph Calendar API

findMeetingTimes suggests slots across attendees and rooms, getSchedule returns free/busy for many people, and transactionId stops a retried create from double-booking. Each app gets four concurrent requests per mailbox. Microsoft published eight Critical, already mitigated CVEs for Exchange Online and Graph in 2026, and the JavaScript client's two security fixes remain unreleased.

Before you call either

Cronofy API

  1. Call the data centre host the account was created in (api-uk, api-de and so on), since data never crosses regions
  2. Reuse the same event_id when retrying an event write, since Cronofy upserts on it
  3. Ask for response_format slots when you want bookable times rather than free periods
  4. On 423, ask the user to relink, since Cronofy has already emailed them
  5. Keep under 50 requests a second and 500 a minute, and pause on 429

Microsoft Graph Calendar API

  1. Send Prefer: outlook.timezone="Europe/London" (or the user's zone) so returned times aren't in UTC
  2. Set a transactionId on event creates so a retry doesn't double-book
  3. Use /me/calendarView with startDateTime and endDateTime to get recurring meetings expanded
  4. Honour Retry-After on 429 and keep to 4 parallel calls per mailbox
  5. Treat event bodies as untrusted input, and ask for Calendars.ReadBasic when you don't need them

Questions

Which is better for AI agents, Cronofy API or Microsoft Graph Calendar API?

Cronofy API scores 69.4 (B) on agent readiness against Microsoft Graph Calendar API's 60.9 (C), and leads in 1 of 7 scored categories. Microsoft Graph Calendar API leads on schema & documentation, agent ergonomics, security & auth, payments & pricing and maintenance & community.

Do Cronofy API and Microsoft Graph Calendar API need an API key?

Cronofy API takes an API key or an OAuth sign-in. Microsoft Graph Calendar API uses an OAuth sign-in.

Can an agent call Cronofy API and Microsoft Graph Calendar API without installing anything?

Yes. Cronofy API has a hosted endpoint at https://api.cronofy.com and Microsoft Graph Calendar API at https://graph.microsoft.com/v1.0.

Other comparisons with Cronofy API or Microsoft Graph Calendar API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.