Get an audit

Head to head · Calendar read · October 2026 research run

Aurinko Calendar API vs Nylas Calendar and Scheduler API

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.

Aurinko Calendar APIYoxel, Inc. · HTTP API E45.6/100#654 of 722 Nylas Calendar and Scheduler APINylas · HTTP API BB71/100#121 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Nylas Calendar and Scheduler API BB

Good 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

  • Reliability, 75 against 40
  • Schema & documentation, 91 against 66
  • Agent ergonomics, 71 against 56
  • Security & auth, 59 against 41
  • Maintenance & community, 88 against 20
  • Transparency & trust, 76 against 44

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

Watch for

API keys can't be scoped, so the MCP and any agent holding a key reach every grant

Score by category

CategoryWeight this runAurinko Calendar APINylas Calendar and Scheduler APIEdge
Reliability16%204075Nylas Calendar and Scheduler API +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26691Nylas Calendar and Scheduler API +25
Agent ergonomics13%16.25671Nylas Calendar and Scheduler API +15
Security & auth14%17.54159Nylas Calendar and Scheduler API +18
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82088Nylas Calendar and Scheduler API +68
Transparency & trust7%8.84476Nylas Calendar and Scheduler API +32
Negative events≤1500
Total45.6 · E71 · BB

Facts side by side

FactAurinko Calendar APINylas Calendar and Scheduler API
KindHTTP APIHTTP API
VendorYoxel, Inc.Nylas
Hosted endpointhttps://api.aurinko.iohttps://api.us.nylas.com/v3
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Yoxel's Terms of Services AgreementMIT (SDKs)
Tools exposednone38
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-09-30
Terms last updated2022-08-112025-06-23
Privacy policy last updated2022-08-112026-01-06
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes
Popularitynone181 stars, 281k npm/wk, 104k PyPI/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.

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.

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

Nylas Calendar and Scheduler API

  1. Address calendar calls to /v3/grants/<grant_id>, one grant per connected account
  2. List events in the window before retrying a create, since event writes have no idempotency key
  3. Point the MCP client at mcp.eu.nylas.com if the application lives in the EU region
  4. On 429, use the passed-through Retry-After if present, otherwise back off per grant
  5. Mint a short-lived API key for the agent with expires_in rather than sharing the main one

Questions

Which is better for AI agents, Aurinko Calendar API or Nylas Calendar and Scheduler API?

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.

Do Aurinko Calendar API and Nylas Calendar and Scheduler API need an API key?

Aurinko Calendar API uses an OAuth sign-in. Nylas Calendar and Scheduler API takes an API key or an OAuth sign-in.

Can an agent call Aurinko Calendar API and Nylas Calendar and Scheduler API without installing anything?

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.

Other comparisons with Aurinko Calendar API or Nylas Calendar and Scheduler 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