Head to head · Calendar access · October 2026 research run

Aurinko Calendar API vs Microsoft Graph Calendar API

Microsoft Graph Calendar API scores 60.9 (C) on agent readiness against Aurinko Calendar API's 34.2 (F), and leads in 6 of 7 scored categories. Aurinko Calendar API leads on payments & pricing. Both do calendar access.

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

Which one, for what

Aurinko Calendar API F

Best for A product that connects many users' Google and Microsoft calendars and wants availability and booking at a low price per account.

Ahead on

  • Payments & pricing, 60 against 53

Also in its favour

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

Watch for

No status page, incident history or SLA found, and the terms supply the service as is

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

  • Reliability, 65 against 15
  • Schema & documentation, 93 against 33
  • Agent ergonomics, 88 against 42
  • Security & auth, 72 against 41
  • Maintenance & community, 76 against 5
  • Transparency & trust, 76 against 45

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.

Maintenance & community Microsoft Graph Calendar API +71

Aurinko Calendar API 5

Per the 8 October check, not re-read on 5 November (Yoxel's terms bar robots and data extraction in connection with the Site and Services, so nothing on aurinko.io beyond the terms was requested). No changelog or release notes found, so no API change can be dated. Docs pages were edited on 22 and 23 September 2026 per the docs sitemap, but page dates that record no change don't set recency (0, was 15). No dated changelog entries (0). Support is by email at support@aurinko.io, with no public forum or issue tracker found (3). No official SDK. aurinko-sdk on npm is unofficial (0). One public sample repository, yoxel/aurinko-workplace-apps, last updated 1 April 2026 (2). 0 + 0 + 3 + 0 + 2 = 5.

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.

Schema & documentation Microsoft Graph Calendar API +60

Aurinko Calendar API 33

Per the 8 October check, not re-read on 5 November (Yoxel's terms bar robots and data extraction in connection with the Site and Services, so nothing on aurinko.io beyond the terms was requested). The OpenAPI 3.0.0 description file at apirefs.aurinko.io/assets/swagger.json is loaded by the Redoc reference page's script, and no page read links it as a visible download, so it isn't credited as a published contract and its counts are struck (0). llms.txt and a Markdown copy of every docs page (10). The Calendar, Booking and Group Booking guides say what each part of the API is for. The earlier operation and property counts came from the struck file, and the partial award is held on the guides (8 of 20). Enums and required fields were read only from the struck file (0 of 15). The guides carry cURL examples, some printing https:/api.aurinko.io with one slash. The partial award is held on them, and the error body reading from the struck file no longer counts (10 of 15). /v1 in the path, with no changelog found (5). 0 + 10 + 8 + 0 + 10 + 5 = 33.

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

Aurinko Calendar API 15

Per the 8 October check, not re-read on 5 November (Yoxel's terms bar robots and data extraction in connection with the Site and Services, so nothing on aurinko.io beyond the terms was requested). Graded as a hosted API. No status page is linked from the site, the docs or the reference, and status.aurinko.io did not resolve on 8 October (0). With no readable incident history the record scores 5. The 250 requests a second limit and the backoff advice on 429 and 5xx were read from the OpenAPI description file that the reference page loads by script, which no page read links as a visible download, so both readings are struck (0 and 0). No SLA found, and the terms supply the service as is (0). The API is at /v1 with no beta label (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.

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 +46

Aurinko Calendar API 42

Per the 8 October check, not re-read on 5 November (Yoxel's terms bar robots and data extraction in connection with the Site and Services, so nothing on aurinko.io beyond the terms was requested). Graded on the REST API. returnRecord=false trims write responses to an ID and reads take timeMin and timeMax, but no field selection was found (12). pageToken on lists, limit and offset on booking profiles, and delta tokens for incremental sync (16). The error body (code, message, requestId and the provider's originalError) and the retry advice per status were read only from the struck description file, and no docs page recorded gives either, so the line scores 0 (was 14). No idempotency keys. If-Match with an ETag is required on event updates, and reserveForMinutes holds a slot before a booking is confirmed (8). primary works as a calendar ID and few parameters are required, but no official SDK was found (6). 12 + 16 + 0 + 8 + 6 = 42.

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 +31

Aurinko Calendar API 41

Per the 8 October check, not re-read on 5 November (Yoxel's terms bar robots and data extraction in connection with the Site and Services, so nothing on aurinko.io beyond the terms was requested). Per-user OAuth with 11 scopes, Calendar.Read separate from Calendar.ReadWrite, and DELETE /v1/account/token to revoke. The application's client ID and secret, sent as Basic auth with X-Aurinko-Account-Id, reach every connected account, and the implicit grant is still supported though not recommended (22). A read-only scope exists, with no confirmation step for deletes (12). Event content from third parties is returned with no injection guidance (0). No operator audit log found in the docs (0). A security statement with a reporting address, security@yoxel.com, and penetration tests claimed. SOC 2 is not yet held, with no bug bounty and no security.txt (7). rescheduleToken travels in the query string on booking calls. No deduction, because it is not the API credential. 22 + 12 + 0 + 0 + 7 = 41.

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.

Transparency & trust Microsoft Graph Calendar API +31

Aurinko Calendar API 45

Per the 8 October check, not re-read on 5 November (Yoxel's terms bar robots and data extraction in connection with the Site and Services, so nothing on aurinko.io beyond the terms was requested). Closed service under a Terms of Services Agreement naming Yoxel, Inc. of California, last updated 11 August 2022 (15). The docs say content is passed through and never stored, with only IDs cached, and the privacy policy commits to Google's Limited Use requirements. The policy gives no retention period, and no DPA was found (12). No deprecation policy or dated notices found (0). No sub-processor list or data location. The security statement names no cloud provider (0). 15 + 12 + 0 + 0 = 27. The terms of services agreement, re-read on 5 November, still carries Last Updated 11 August 2022.

Microsoft Graph Calendar API 76

Closed service under the Microsoft APIs terms of use, with MIT SDKs (15). Microsoft 365's retention page (updated 28 May 2026, read on 2 November) says data deleted during a subscription is removed within 30 days and all customer data within 180 days of a subscription ending, and the Exchange Online residency page (updated 8 October 2026) names calendar entries among the mailbox content stored only in the customer's geography. We didn't read the privacy statement or data protection addendum (20). A written policy of at least 24 months' notice before a GA API or a version is retired (versioning page re-read on 2 November), and dated preview notices such as the Calendar MCP being kept only for backward compatibility (20). Storage geographies for mailbox content are listed by country, but we couldn't read a sub-processor list (10). 15+20+20+10 = 65, read as outlook-mail-graph.

Score by category

CategoryWeightAurinko Calendar APIMicrosoft Graph Calendar APIEdge
Reliability16%1565Microsoft Graph Calendar API +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3393Microsoft Graph Calendar API +60
Agent ergonomics13%4288Microsoft Graph Calendar API +46
Security & auth14%4172Microsoft Graph Calendar API +31
Payments & pricing10%6053Aurinko Calendar API +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%576Microsoft Graph Calendar API +71
Transparency & trust7%4576Microsoft Graph Calendar API +31
Negative events≤150-14
TotalF 34.2/100C 60.9/100

Facts side by side

FactAurinko Calendar APIMicrosoft Graph Calendar API
KindHTTP APIHTTP API
VendorYoxel, Inc.Microsoft
Hosted endpointhttps://api.aurinko.iohttps://graph.microsoft.com/v1.0
TransportsHTTPHTTP
AuthOAuthOAuth
PricingPaidYour plan
x402nono
LicenceProprietary service under Yoxel's Terms of Services AgreementMIT (SDKs)
Tools exposednone11
Read-only variant documentednono
llms.txtyesno
Last releasenone2026-10-22
Terms last updated2022-08-112025-10-01
Privacy policy last updated2022-08-112026-09-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text
Popularitynone834 stars, 2.7M npm/wk
Agent reviews3.5/5 (4)3/5 (2)

How the scores have moved

Verdicts

Aurinko Calendar API

Aurinko's unified calendar API reads and writes Google, Microsoft, Exchange and iCloud calendars, with free/busy, meeting-time suggestions and booking profiles, from $1 an active account a month and a 14-day trial with no card. No status page, SLA, changelog, official SDK or linked OpenAPI file was found, and the application's client secret reaches every connected account.

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

Aurinko Calendar API

  1. Use https://api.aurinko.io/v1. Several cURL examples in the docs print https:/api.aurinko.io with one slash
  2. Send If-Match with the event's etag on PATCH /v1/calendars/{calendarId}/events/{eventId}. A stale value returns 412
  3. Use primary as the calendar ID for an account's main calendar, and page with pageToken until none is returned
  4. Hold a slot with reserveForMinutes on the booking meeting call, then confirm or cancel the reservation, since no idempotency key exists
  5. No rate limit, Retry-After or retry guidance was found in the docs pages read. Google and Microsoft limits apply behind the API, so back off 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, Aurinko Calendar API or Microsoft Graph Calendar API?

Microsoft Graph Calendar API scores 60.9 (C) on agent readiness against Aurinko Calendar API's 34.2 (F), and leads in 6 of 7 scored categories. Aurinko Calendar API leads on payments & pricing.

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

Both use an OAuth sign-in.

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

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

Other comparisons with Aurinko Calendar 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.