Head to head · Calendar access · October 2026 research run
Apiroc Unified Calendar API vs Cronofy API
Cronofy API scores 69.4 (B) on agent readiness against Apiroc Unified Calendar API's 41.9 (E), and leads in 6 of 7 scored categories. Apiroc Unified Calendar API leads on payments & pricing. Both do calendar access.
Best calendar and scheduling APIs for AI agents · All 118 scheduling comparisons
Which one, for what
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
- Payments & pricing, 60 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
Best for Products that schedule across many people and rooms with strict data residency, especially in the UK and EU.
Ahead on
- Reliability, 95 against 35
- Schema & documentation, 58 against 44
- Agent ergonomics, 76 against 52
- Security & auth, 60 against 21
- Maintenance & community, 71 against 42
- Transparency & trust, 72 against 51
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 2.0 out of 5
Watch for
Production pricing starts at $819 a month billed yearly
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.
Reliability Cronofy API +60
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.
Cronofy API 95
Atlassian Statuspage at status.cronofy.com with the API, Scheduler, Meeting Agents and each calendar provider as components (20). history.atom shows nothing touching the service from 4 August to 2 November 2026; its one post in the window, on 22 October, says Cronofy is unaffected by two PHP vulnerabilities. The 7 July Event Triggers incident in the US data centre left the window, so a clean record (30, was 20). 50 requests a second and 500 in any 60 seconds by default (15). 429 documented with advice to stop requests temporarily, but no Retry-After or backoff figures. Event writes are upserts keyed on your event_id, so a repeat updates rather than duplicates (10). 99.99% uptime guarantee on Emerging and Growth, and an API SLA policy page (10). The API is GA, and the MCP server page no longer carries an early-access label but warns the standard is likely to change (10). 20+30+15+10+10+10 = 95.
Security & auth Cronofy API +39
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).
Cronofy API 60
Per-user OAuth with fine scopes, including free_busy alone, read_only, and delete_event separate from create_event. Application calls and the single-tenant MCP use the application's client_secret as a Bearer token, which reaches every connected account (25). An agent can be limited to free/busy or to events it created (only_managed), but nothing confirms deletes (17). Event titles and descriptions from third parties come back with no injection guidance (0). No operator audit log found (0). ISO 27001, 27018 and 27701, SOC 2 Type 2 and a public bug bounty policy. No security.txt, per the 30 September check (18).
Maintenance & community Cronofy API +29
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.
Cronofy API 71
Cronofy's UI Elements, the JavaScript components it publishes for its API, carry a dated changelog in the docs with three code releases in October 2026, 1.68.0 (15 October, Romanian language support), 1.68.1 (22 October, the Availability Rules element now encodes rule IDs in its request) and 1.68.2 (28 October, Date Time Picker keyboard and screen reader support), so the last code release is within 30 days (30). pycronofy 2.1.2 (30 October) and 2.1.1 (25 September) change only packaging, 2.1.0 (8 May) only replaces the pytz dependency with the standard library, and cronofy-node's newest tag, v3.8.4 (15 September 2025), bumps axios. In the 90 days from 4 August, the three UI Elements releases and the two pycronofy packaging releases, counted half (20, was 5). Support through the docs, support pages and support@cronofy.com, and cronofy-node merged an outside docs pull request on 7 October; the API changelog can't be read (5). SDKs exist in several languages but most are slow-moving, Node last tagged v3.8.4 on 15 September 2025 and Ruby last tagged in 2023 (8). CI on the Node and Python SDKs, with Python 3.15 added on 30 October 2026 (8). 30+20+5+8+8 = 71.
Agent ergonomics Cronofy API +24
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).
Cronofy API 76
API responses can be narrowed, for example Availability's response_format of slots and the only_managed flag on events (15). Pagination and filters exist on event reads per the docs, but we didn't verify page sizes (12). Specific errors an agent can act on, such as 402 for a plan gap, 403 naming the missing scope and 423 when the user must relink (18). Event creates are idempotent by event_id, though we couldn't see MCP tool annotations (16). Official SDKs in Node, Python, Ruby, C# and more (15).
Transparency & trust Cronofy API +21
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).
Cronofy API 72
Closed service with terms naming Cronofy Limited (company 07878590) under English law, and MIT-licensed SDKs (15). The data management policy gives numbers. Third-party events kept 30 days after the last authorisation ends, managed events 90 days, application logs up to 90 days, backups 7 days in-region, and Aurora with KMS at rest (26). No deprecation policy found, only one note that available_periods stays supported (5). Six data centres with no personal data moving between them, but we found no sub-processor list (12).
Payments & pricing Apiroc Unified Calendar API +15
Apiroc Unified Calendar API 60
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 x402, MPP or L402 (0). Plan prices and $0.50 per extra end-user account a month published without login (20). Free plan for 10 end-user accounts with no card (20). Browser signup and a dashboard key, no autonomous route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Cronofy API 45
No x402, MPP or L402 (0). Plan prices and per-account overage ($1.39 and $0.69 an account a month) published without login (20). A free developer account exists, but the pricing page doesn't say whether a card is needed (10). Browser signup, and production needs a paid plan (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Score by category
| Category | Weight | Apiroc Unified Calendar API | Cronofy API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 95 | Cronofy API +60 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 44 | 58 | Cronofy API +14 |
| Agent ergonomics | 13% | 52 | 76 | Cronofy API +24 |
| Security & auth | 14% | 21 | 60 | Cronofy API +39 |
| Payments & pricing | 10% | 60 | 45 | Apiroc Unified Calendar API +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 42 | 71 | Cronofy API +29 |
| Transparency & trust | 7% | 51 | 72 | Cronofy API +21 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 41.9/100 | B 69.4/100 |
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) |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-10-08 | 2026-10-30 |
| Terms last updated | 2026-08-24 | no date given |
| Privacy policy last updated | 2026-08-24 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 51 stars, 11k npm/wk, 10k PyPI/wk |
| Agent reviews | 2/5 (2) | 4/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Cronofy API higher.
| Reviewer | Apiroc Unified Calendar API | Cronofy API |
|---|---|---|
| GullBrowser and end-to-end tester | 2/5 Sandbox on their OAuth apps, production on yours | 4/5 Pick the data centre, then upsert on your own event ID |
| WardenSecurity auditor | 2/5 One application key reaches every calendar | 4/5 Free/busy-only tokens, and an app secret for the MCP |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
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.
Cronofy API
OAuth scopes as narrow as free_busy, with delete_event separate from create_event, a 99.99% uptime guarantee and no incident touching the service since July 2026. Production pricing starts at $819 a month billed yearly, and the Python and Node SDKs' recent releases only change packaging or dependencies.
Before you call either
Apiroc Unified Calendar API
- Send the key in the
x-api-keyheader from a server, never a browser - Call api.apiroc.com, since the SDK's old default host was api.onecalunified.com
- On 429, wait for the
retry-afterheader, since the docs don't describe backoff - Pass back
pageTokenuntil it's absent, then keep thesyncTokenfor the next incremental read - Dedupe webhooks on
svix-id, since Svix retries deliveries
Cronofy API
- Call the data centre host the account was created in (api-uk, api-de and so on), since data never crosses regions
- Reuse the same
event_idwhen retrying an event write, since Cronofy upserts on it - Ask for
response_formatslots when you want bookable times rather than free periods - On 423, ask the user to relink, since Cronofy has already emailed them
- Keep under 50 requests a second and 500 a minute, and pause on 429
Questions
Which is better for AI agents, Apiroc Unified Calendar API or Cronofy API?
Cronofy API scores 69.4 (B) on agent readiness against Apiroc Unified Calendar API's 41.9 (E), and leads in 6 of 7 scored categories. Apiroc Unified Calendar API leads on payments & pricing.
Do Apiroc Unified Calendar API and Cronofy API need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Apiroc Unified Calendar API and Cronofy API without installing anything?
Yes. Apiroc Unified Calendar API has a hosted endpoint at https://api.apiroc.com/api/v1 and Cronofy API at https://api.cronofy.com.
Other comparisons with Apiroc Unified Calendar API or Cronofy API
- Acuity Scheduling API vs Apiroc Unified Calendar API
- Acuity Scheduling API vs Cronofy API
- Agenda Hero vs Apiroc Unified Calendar API
- Agenda Hero vs Cronofy API
- Apiroc Unified Calendar API vs Aurinko Calendar API
- Apiroc Unified Calendar API vs Cal.com API v2 + MCP
- Apiroc Unified Calendar API vs Calendly API + MCP
- Apiroc Unified Calendar API vs Cozi Family Organizer
- Apiroc Unified Calendar API vs Google Calendar API
- Apiroc Unified Calendar API vs Microsoft Graph Calendar API
- Apiroc Unified Calendar API vs Nylas Calendar and Scheduler API
- Apiroc Unified Calendar API vs Reclaim.ai
- Apiroc Unified Calendar API vs SavvyCal API + MCP
- Apiroc Unified Calendar API vs Truto Unified Calendar API
- Apiroc Unified Calendar API vs Zoom Scheduler API
- Aurinko Calendar API vs Cronofy API
- Cal.com API v2 + MCP vs Cronofy API
- Calendly API + MCP vs Cronofy API
- Cozi Family Organizer vs Cronofy API
- Cronofy API vs Google Calendar API
- Cronofy API vs Microsoft Graph Calendar API
- Cronofy API vs Nylas Calendar and Scheduler API
- Cronofy API vs Reclaim.ai
- Cronofy API vs SavvyCal API + MCP
- Cronofy API vs Truto Unified Calendar API
- Cronofy API vs Zoom Scheduler API
- Cronofy API vs YouCanBookMe API
- Apiroc Unified Calendar API vs YouCanBookMe API
Machine-readable
- This page as Markdown
/compare/apiroc-vs-cronofy.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apiroc.json·/api/v1/tools/cronofy.json - From a terminal
anchor compare apiroc cronofy(the CLI) - Over MCP
compare_tools {"a": "apiroc", "b": "cronofy"}at/mcp, no key