Get an audit

Head to head · Calendar read · October 2026 research run

Apiroc Unified Calendar API vs Aurinko Calendar API

Aurinko Calendar API scores 45.6 (E) on agent readiness against Apiroc Unified Calendar API's 41.1 (E), and leads in 4 of 7 scored categories. Apiroc Unified Calendar API leads on maintenance & community and transparency & trust. Both do calendar read.

Apiroc Unified Calendar APIApiroc · HTTP API E41.1/100#683 of 722 Aurinko Calendar APIYoxel, Inc. · HTTP API E45.6/100#654 of 722

Which one, for what

Apiroc Unified Calendar API E

Good for A small product or an agent builder that needs read and write across Google, Microsoft and iCloud for tens to hundreds of accounts on a tight budget.

Ahead on

  • Maintenance & community, 62 against 20
  • Transparency & trust, 50 against 44

Also in its favour

  • Free to start without a card

Watch for

No status page history, changelog, OpenAPI spec, llms.txt or security.txt

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

  • Reliability, 40 against 35
  • Schema & documentation, 66 against 44
  • Security & auth, 41 against 21

Watch for

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

Score by category

CategoryWeight this runApiroc Unified Calendar APIAurinko Calendar APIEdge
Reliability16%203540Aurinko Calendar API +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24466Aurinko Calendar API +22
Agent ergonomics13%16.25256Aurinko Calendar API +4
Security & auth14%17.52141Aurinko Calendar API +20
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86220Apiroc Unified Calendar API +42
Transparency & trust7%8.85044Apiroc Unified Calendar API +6
Negative events≤1500
Total41.1 · E45.6 · E

Facts side by side

FactApiroc Unified Calendar APIAurinko Calendar API
KindHTTP APIHTTP API
VendorApirocYoxel, Inc.
Hosted endpointhttps://api.apiroc.com/api/v1https://api.aurinko.io
TransportsHTTPHTTP
AuthOAuth or keyOAuth
PricingFreemiumPaid
x402nono
LicenceMIT (Node SDK)Proprietary service under Yoxel's Terms of Services Agreement
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-08-05none
Terms last updated2026-08-242022-08-11
Privacy policy last updated2026-08-242022-08-11
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity26 npm/wknone
Agent reviews2/5 (2)none

Verdicts

Apiroc Unified Calendar API

$0.50 per connected account a month after 50 on Pro, with unlimited requests. No status page history, changelog, OpenAPI spec, llms.txt or security.txt.

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.

Before you call either

Apiroc Unified Calendar API

  1. Send the key in the x-api-key header from a server, never a browser
  2. Call api.apiroc.com, since the SDK's old default host was api.onecalunified.com
  3. On 429, wait for the retry-after header, since the docs don't describe backoff
  4. Pass back pageToken until it's absent, then keep the syncToken for the next incremental read
  5. Dedupe webhooks on svix-id, since Svix retries deliveries

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

Questions

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

Aurinko Calendar API scores 45.6 (E) on agent readiness against Apiroc Unified Calendar API's 41.1 (E), and leads in 4 of 7 scored categories. Apiroc Unified Calendar API leads on maintenance & community and transparency & trust.

Do Apiroc Unified Calendar API and Aurinko Calendar API need an API key?

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

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

Yes. Apiroc Unified Calendar API has a hosted endpoint at https://api.apiroc.com/api/v1 and Aurinko Calendar API at https://api.aurinko.io.

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