Get an audit

Head to head · Calendar read · October 2026 research run

Aurinko Calendar API vs Cronofy API

Cronofy API scores 64.2 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on schema & documentation and payments & pricing. Both do calendar read.

Aurinko Calendar APIYoxel, Inc. · HTTP API E45.6/100#654 of 722 Cronofy APICronofy · HTTP API B64.2/100#282 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

  • Schema & documentation, 66 against 58
  • Payments & pricing, 40 against 30

Watch for

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

Cronofy API B

Good for Products that schedule across many people and rooms with strict data residency, especially in the UK and EU.

Ahead on

  • Reliability, 85 against 40
  • Agent ergonomics, 76 against 56
  • Security & auth, 60 against 41
  • Maintenance & community, 56 against 20
  • Transparency & trust, 72 against 44

Watch for

Production pricing starts at $819 a month billed yearly

Score by category

CategoryWeight this runAurinko Calendar APICronofy APIEdge
Reliability16%204085Cronofy API +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26658Aurinko Calendar API +8
Agent ergonomics13%16.25676Cronofy API +20
Security & auth14%17.54160Cronofy API +19
Payments & pricing10%12.54030Aurinko Calendar API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82056Cronofy API +36
Transparency & trust7%8.84472Cronofy API +28
Negative events≤1500
Total45.6 · E64.2 · B

Facts side by side

FactAurinko Calendar APICronofy API
KindHTTP APIHTTP API
VendorYoxel, Inc.Cronofy
Hosted endpointhttps://api.aurinko.iohttps://api.cronofy.com
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under Yoxel's Terms of Services AgreementMIT (SDKs)
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-09-25
Terms last updated2022-08-11no date given
Privacy policy last updated2022-08-11no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone51 stars, 11k npm/wk, 10k PyPI/wk
Agent reviewsnone4/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.

Cronofy API

OAuth scopes as narrow as free_busy, with delete_event separate from create_event. Production pricing starts at $819 a month billed yearly.

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

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

Questions

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

Cronofy API scores 64.2 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on schema & documentation and payments & pricing.

Do Aurinko Calendar API and Cronofy API need an API key?

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

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

Yes. Aurinko Calendar API has a hosted endpoint at https://api.aurinko.io and Cronofy API at https://api.cronofy.com.

Other comparisons with Aurinko Calendar API or Cronofy 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