Get an audit

Head to head · Calendar read · October 2026 research run

Aurinko Calendar API vs Microsoft Graph Calendar API

Microsoft Graph Calendar API scores 65.1 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Aurinko Calendar API leads on payments & pricing. Both do calendar read.

Aurinko Calendar APIYoxel, Inc. · HTTP API E45.6/100#654 of 722 Microsoft Graph Calendar APIMicrosoft · HTTP API B65.1/100#264 of 722

Which one, for what

Aurinko Calendar API E

Good 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, 40 against 35

Also in its favour

  • No incidents deducted, where Microsoft Graph Calendar API loses 4 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 B

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

Ahead on

  • Reliability, 65 against 40
  • Schema & documentation, 83 against 66
  • Agent ergonomics, 88 against 56
  • Security & auth, 65 against 41
  • Maintenance & community, 76 against 20
  • Transparency & trust, 68 against 44

Watch for

4 concurrent requests per app per mailbox

Score by category

CategoryWeight this runAurinko Calendar APIMicrosoft Graph Calendar APIEdge
Reliability16%204065Microsoft Graph Calendar API +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26683Microsoft Graph Calendar API +17
Agent ergonomics13%16.25688Microsoft Graph Calendar API +32
Security & auth14%17.54165Microsoft Graph Calendar API +24
Payments & pricing10%12.54035Aurinko Calendar API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82076Microsoft Graph Calendar API +56
Transparency & trust7%8.84468Microsoft Graph Calendar API +24
Negative events≤150-4
Total45.6 · E65.1 · B

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-07-17
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 reviewsnone3/5 (2)

Verdicts

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.

Microsoft Graph Calendar API

findMeetingTimes suggests slots across attendees and rooms, and getSchedule returns free/busy for many people. 4 concurrent requests per app per mailbox.

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. Retry 429, 408 and 5xx with exponential backoff. Do not retry 404. A 429 can come from Google or Microsoft limits behind the API

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. Ask for Calendars.ReadBasic when you don't need event bodies

Questions

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

Microsoft Graph Calendar API scores 65.1 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), 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.

Get an auditSee a sample report