Head to head · Calendar access · October 2026 research run

Apiroc Unified Calendar API vs Aurinko Calendar API

Apiroc Unified Calendar API scores 41.9 (E) on agent readiness against Aurinko Calendar API's 34.2 (F), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on security & auth. Both do calendar access.

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

Which one, for what

Apiroc Unified Calendar API E

Best 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

  • Reliability, 35 against 15
  • Schema & documentation, 44 against 33
  • Agent ergonomics, 52 against 42
  • Maintenance & community, 42 against 5
  • Transparency & trust, 51 against 45

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

  • Security & auth, 41 against 21

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

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

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 Apiroc Unified Calendar API +37

Apiroc Unified Calendar API 42

Node SDK v2.1.0, tagged on 8 October 2026 ("feat: add caldav support", connecting any CalDAV server), 33 days before this check (20). From 12 August only that one release; v1.2.2 (14 July) and v1.3.0, v2.0.0 and v2.0.1 (5 August) are now outside the 90 days, and no changelog or other dated source of Apiroc's could be read (0; was 20). No public changelog. Support by email, with priority support on Pro and a Slack channel on Enterprise, per the 1 October check (4). One current official SDK, in Node (10). CI typechecks, lints, builds and tests on pull requests, a tag-triggered workflow publishes to npm, and dependencies were last bumped in May 2026 (8). 20 + 0 + 4 + 10 + 8 = 42.

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.

Reliability Apiroc Unified Calendar API +20

Apiroc Unified Calendar API 35

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. No public status page with history. status.apiroc.com doesn't resolve and the homepage shows only an "All systems operational" badge with a claim of 34B+ API calls (0). No readable incident history (5). Rate limits published with numbers, 20 requests a second in Sandbox and 300 in Production per application, plus 600 a minute per Google account and 1,000 a minute per Microsoft account (15). The docs don't mention 429 or Retry-After, though the official Node SDK reads a retry-after header on 429, and webhook docs say to dedupe on svix-id (5). The terms say availability can't be guaranteed, and no SLA was found on any plan (0). GA, with production use licensed on Pro (10). The 429 line's 5 is an in-between value kept from 1 October (the SDK reads retry-after, the docs say nothing). 0 + 5 + 15 + 5 + 0 + 10 = 35.

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.

Security & auth Aurinko Calendar API +20

Apiroc Unified Calendar API 21

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. Your application calls with one x-api-key that reaches every connected end-user account, and we found no key scopes or rotation docs (10). Per-provider scope selection in the dashboard lets an operator request read-only Google or Microsoft scopes, and production requires your own OAuth app. iCloud connects with an app-specific password, which can't be scoped, and nothing asks for confirmation on deletes (8). Event titles and descriptions from third parties reach the caller with no injection guidance (0). Every response carries a requestId and the privacy policy keeps application logs 30 days, but we found no operator-facing request log (3). No security.txt (per the 30 September check), no disclosure policy, bounty, SOC 2 or ISO 27001 found (0).

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.

Schema & documentation Apiroc Unified Calendar API +11

Apiroc Unified Calendar API 44

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. No OpenAPI spec. A Postman collection is the only machine-readable contract (10). No llms.txt, per the 30 September check (0). Reference pages for five resources with parameters and cURL, TypeScript and Python examples, but little on when to use one endpoint over another (10). Typed inputs in the Node SDK and required fields marked in the docs (10). Examples throughout, and an errors page that gives only the shape (error, message, requestId) and the 2xx, 4xx and 5xx ranges, with no list of error names (9). /v1 in the path but no changelog (5).

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.

Agent ergonomics Apiroc Unified Calendar API +10

Apiroc Unified Calendar API 52

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. Lists take limit and pageToken, and event reads return a syncToken for incremental sync (15). Pagination and sync tokens, with free/busy as a separate endpoint (15). Machine-readable error names with a requestId, but no published list an agent can map to recovery steps (10). No idempotency keys. Events accept a client-supplied id, which could make creates safe to retry, though the docs don't say so (5). Node is the only SDK. Python, PHP and Java are listed as on the way (7).

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.

Transparency & trust Apiroc Unified Calendar API +6

Apiroc Unified Calendar API 51

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. Closed service with terms under Albanian law and an MIT Node SDK (15). Privacy policy (24 August 2026) says event content isn't stored persistently, application logs and analytics are kept 30 days, data isn't used to train models, and Google's Limited Use rules apply. A DPA is published. Webhooks are delivered through Svix, which isn't on the sub-processor list, and webhook message retention has no period (18). 30 days' notice for price rises and sub-processor changes, but no API deprecation policy (3). Five sub-processors listed with locations, and servers stated as US. Svix missing (15).

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.

Score by category

CategoryWeightApiroc Unified Calendar APIAurinko Calendar APIEdge
Reliability16%3515Apiroc Unified Calendar API +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4433Apiroc Unified Calendar API +11
Agent ergonomics13%5242Apiroc Unified Calendar API +10
Security & auth14%2141Aurinko Calendar API +20
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%425Apiroc Unified Calendar API +37
Transparency & trust7%5145Apiroc Unified Calendar API +6
Negative events≤1500
TotalE 41.9/100F 34.2/100

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-10-08none
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
Agent reviews2/5 (2)3.5/5 (4)

How the scores have moved

Verdicts

Apiroc Unified Calendar API

$0.50 per connected account a month after 50 on Pro, with unlimited requests, and Google, Outlook, iCloud and other CalDAV servers behind one schema. No status page history, changelog, OpenAPI spec, llms.txt or security.txt was found, and one application key reaches every connected account.

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.

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. 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

Questions

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

Apiroc Unified Calendar API scores 41.9 (E) on agent readiness against Aurinko Calendar API's 34.2 (F), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on security & auth.

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.