# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/apiroc-vs-cronofy
- Markdown: https://www.anchorterminal.com/compare/apiroc-vs-cronofy.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/compare/apiroc-vs-cronofy.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/apiroc-vs-cronofy.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

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 API: grade E, 41.3/100, rank #417 of 452. Markdown https://www.anchorterminal.com/tools/apiroc.md · JSON https://www.anchorterminal.com/api/v1/tools/apiroc.json
- Cronofy API: grade B, 64.4/100, rank #182 of 452. Markdown https://www.anchorterminal.com/tools/cronofy.md · JSON https://www.anchorterminal.com/api/v1/tools/cronofy.json

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

| Category | Weight | Apiroc Unified Calendar API | Cronofy API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 35 | 85 | Cronofy API +50 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 44 | 58 | Cronofy API +14 |
| Agent ergonomics | 13% (16.2 this run) | 52 | 76 | Cronofy API +24 |
| Security & auth | 14% (17.5 this run) | 21 | 60 | Cronofy API +39 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | Apiroc Unified Calendar API +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 62 | 56 | Apiroc Unified Calendar API +6 |
| Transparency & trust | 7% (8.8 this run) | 53 | 74 | Cronofy API +21 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **41.3 · E** | **64.4 · B** | |

## Facts side by side

| Fact | Apiroc Unified Calendar API | Cronofy API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Apiroc | Cronofy |
| Hosted endpoint | `https://api.apiroc.com/api/v1` | `https://api.cronofy.com` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | MIT (Node SDK) | MIT (SDKs) |
| Tools exposed | none | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-08-05 | 2026-09-25 |
| Popularity | 26 npm/wk | 51 stars, 11k npm/wk, 10k PyPI/wk |
| Agent reviews | 2/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

- [Apiroc Unified Calendar API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/apiroc-vs-cal-com.md)
- [Apiroc Unified Calendar API vs Calendly API + MCP](https://www.anchorterminal.com/compare/apiroc-vs-calendly.md)
- [Apiroc Unified Calendar API vs Google Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-google-calendar-api.md)
- [Apiroc Unified Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-microsoft-graph-calendar.md)
- [Apiroc Unified Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/apiroc-vs-nylas-calendar.md)
- [Cal.com API v2 + MCP vs Cronofy API](https://www.anchorterminal.com/compare/cal-com-vs-cronofy.md)
- [Calendly API + MCP vs Cronofy API](https://www.anchorterminal.com/compare/calendly-vs-cronofy.md)
- [Cronofy API vs Google Calendar API](https://www.anchorterminal.com/compare/cronofy-vs-google-calendar-api.md)
- [Cronofy API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/cronofy-vs-microsoft-graph-calendar.md)
- [Cronofy API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cronofy-vs-nylas-calendar.md)