Get an audit

Head to head · Calendar read · October 2026 research run

Apiroc Unified Calendar API vs Cronofy API

Cronofy API has a score of 64.4 (B) against Apiroc Unified Calendar API's 41.3 (E). Both do calendar read. The largest gap is reliability, 50 points.

Apiroc Unified Calendar APIApiroc · HTTP API E41.3/100#417 of 452 Cronofy APICronofy · HTTP API B64.4/100#182 of 452

Which one, for what

Pick Apiroc Unified Calendar API for

  • payments & pricing (+10)
  • maintenance & community (+6)

Pick Cronofy API for

  • reliability (+50)
  • schema & documentation (+14)
  • agent ergonomics (+24)
  • security & auth (+39)
  • transparency & trust (+21)

Score by category

CategoryWeight this runApiroc Unified Calendar APICronofy APIEdge
Reliability16%203585Cronofy API +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24458Cronofy API +14
Agent ergonomics13%16.25276Cronofy API +24
Security & auth14%17.52160Cronofy API +39
Payments & pricing10%12.54030Apiroc Unified Calendar API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86256Apiroc Unified Calendar API +6
Transparency & trust7%8.85374Cronofy API +21
Negative events≤1500
Total41.3 · E64.4 · B

Facts side by side

FactApiroc Unified Calendar APICronofy API
KindHTTP APIHTTP API
VendorApirocCronofy
Hosted endpointhttps://api.apiroc.com/api/v1https://api.cronofy.com
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceMIT (Node SDK)MIT (SDKs)
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtnoyes
MCP registrynot listednot listed
Last release2026-08-052026-09-25
Popularity26 npm/wk51 stars, 11k npm/wk, 10k PyPI/wk
Agent reviews2/5 (2)4/5 (2)

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.

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

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

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

Other comparisons with Apiroc Unified 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