{ "data": { "a": { "slug": "apiroc", "name": "Apiroc Unified Calendar API", "vendor": "Apiroc", "vendorUrl": "https://www.apiroc.com", "kind": "http-api", "category": "scheduling", "summary": "Unified calendar API over Google Calendar, Microsoft Outlook (Office 365, Exchange and Outlook.com) and iCloud.", "url": "https://www.anchorterminal.com/tools/apiroc", "markdownUrl": "https://www.anchorterminal.com/tools/apiroc.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/apiroc.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/apiroc.json", "repo": "https://github.com/OneCal/unified-calendar-api-node-sdk", "license": "MIT (Node SDK)", "transports": [ "http" ], "remoteUrl": "https://api.apiroc.com/api/v1", "packages": [ { "registry": "npm", "name": "@apiroc/unified-calendar-api-node-sdk" } ], "auth": "mixed", "authNotes": "Your application calls the API with an `x-api-key` header, server side only. End users connect Google and Microsoft accounts through OAuth 2.0 and iCloud with an app-specific password.", "pricing": "freemium", "pricingNotes": "Free $0 a month for up to 10 end-user accounts at 20 requests a second, no card. Pro $25 a month with 50 end-user accounts, then $0.50 per account a month, at 300 requests a second and licensed for production use. Enterprise is custom with volume discounts and custom rate limits. Every plan has unlimited API requests and webhooks (https://www.apiroc.com/pricing).", "priceSummary": "$25 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 26, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.apiroc.com", "capabilities": [ "calendar.read", "calendar.write", "calendar.availability", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "webhooks", "typescript" ], "lastRelease": "2026-08-05", "graded": true, "anchor": { "graded": true, "score": 41.3, "grade": "E", "agentReady": false, "rank": 417, "ranked": true, "rankOf": 452, "categoryRank": 7, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 62, "payments": 40, "reliability": 35, "schema": 44, "security": 21, "transparency": 53 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "$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.", "strengths": [ "$0.50 per connected account a month after 50 on Pro, with unlimited requests", "Free plan for 10 accounts with no card", "Google, Outlook (Office 365, Exchange, Outlook.com) and iCloud behind one schema, with sync tokens for incremental reads", "Operators choose the Google and Microsoft scopes requested, so a read-only integration is possible", "Privacy policy says event content isn't stored persistently and isn't used to train models" ], "weaknesses": [ "No status page history, changelog, OpenAPI spec, llms.txt or security.txt", "One application key reaches every connected account, with no key scopes documented", "No SLA on any plan, and no 429 or retry guidance in the docs", "Svix handles webhook delivery but isn't on the sub-processor list", "Node.js is the only SDK" ], "agentNotes": [ "Send the key in the `x-api-key` header 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-after` header, since the docs don't describe backoff", "Pass back `pageToken` until it's absent, then keep the `syncToken` for the next incremental read", "Dedupe webhooks on `svix-id`, since Svix retries deliveries" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.3 } ], "editorialScores": { "ergonomics": 52, "maintenance": 62, "payments": 40, "reliability": 35, "schema": 44, "security": 21, "transparency": 51 }, "provenanceScore": 55 }, "connect": { "http": "curl -G https://api.apiroc.com/api/v1/endUserAccounts -H \"x-api-key: $APIROC_API_KEY\"" }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/apiroc" }, "area": "everyday", "unitPrices": [ { "item": "Pro", "unit": "month", "usd": 25, "note": "50 end-user accounts included" }, { "item": "Extra end-user account on Pro", "unit": "account-month", "usd": 0.5 } ], "provenance": { "legalEntity": "UTC Labs", "domain": "apiroc.com", "domainRegistered": "2026-04-09", "domainNote": "apiroc.com was registered on 2026-04-09. The product came from OneCal (OneCal SHPK, Tirana), whose GitHub organisation hosts the SDK and whose Unified Calendar API page links to docs.apiroc.com.", "endpointOnVendorDomain": true, "terms": "https://www.apiroc.com/tos", "privacy": "https://www.apiroc.com/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "The terms (updated 24 August 2026) name UTC Labs at Durana Tech Park, Shijak, Albania, under Albanian law, with contact@utclabs.com as the contact. No company form or registration number is given.", "onecal.io's privacy policy names OneCal SHPK in Tirana. Neither site names the other's entity.", "status.apiroc.com doesn't resolve. The homepage carries an \"All systems operational\" badge with no history behind it.", "www.apiroc.com/.well-known/security.txt returned 404 on the 30 September check, and docs.apiroc.com/llms.txt returned 404." ], "score": 55 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/apiroc.json", "live": { "slug": "apiroc", "probe": { "target": "https://api.apiroc.com/api/v1", "method": "get", "lastAt": "2026-10-05T02:29:51.600467128Z", "lastOk": true, "lastStatus": 404, "lastMs": 229, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 225, "p95ms24h": 307, "samples24h": 273, "samples30d": 929, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 29, "ok": 29 } ] }, "versions": [ { "registry": "npm", "name": "@apiroc/unified-calendar-api-node-sdk", "version": "2.0.1", "seenAt": "2026-10-04T16:20:41.519616919Z" } ], "githubStars": 2, "npmWeekly": 9, "securityTxt": { "url": "https://apiroc.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:42.565883668Z" }, "domain": { "domain": "apiroc.com", "registered": "2026-04-09", "source": "https://rdap.verisign.com/com/v1/domain/apiroc.com", "checkedAt": "2026-10-04T13:10:05.921989529Z" }, "pages": [ { "url": "https://www.apiroc.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-04T15:49:08.985266078Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "933585cad4b8" }, { "url": "https://www.apiroc.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-04T15:49:12.075622313Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6076c53fc344" }, { "url": "https://www.apiroc.com/tos", "kind": "terms", "status": 200, "checkedAt": "2026-10-04T15:49:13.174399907Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b0e155d5c872" } ], "updatedAt": "2026-10-05T02:29:51.600467128Z" } }, "b": { "slug": "cronofy", "name": "Cronofy API", "vendor": "Cronofy", "vendorUrl": "https://www.cronofy.com", "kind": "http-api", "category": "scheduling", "summary": "Calendar sync and scheduling API from a UK company.", "url": "https://www.anchorterminal.com/tools/cronofy", "markdownUrl": "https://www.anchorterminal.com/tools/cronofy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cronofy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cronofy.json", "repo": "https://github.com/cronofy/cronofy-node", "license": "MIT (SDKs)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.cronofy.com", "packages": [ { "registry": "npm", "name": "cronofy" }, { "registry": "pypi", "name": "pycronofy" } ], "auth": "mixed", "authNotes": "Each user connects through Cronofy's OAuth flow and gets an access token. Application-level calls such as Availability take the application's key as a Bearer token. The MCP server takes the `client_secret` of an internal application as a Bearer token for single-tenant use, or OAuth 2.0 for multi-tenant use.", "pricing": "paid", "pricingNotes": "Free developer account for building and testing. Emerging $819 a month billed yearly for up to 500 synced accounts, then $1.39 each a month. Growth $2,399 a month billed yearly for up to 3,000, then $0.69 each. Strategic is custom with priority support. The Meeting Agents add-on costs $0.79 an hour for 25 to 4,000 hours, with a $99 monthly minimum on its own and the first 24 hours free (https://www.cronofy.com/pricing).", "priceSummary": "$819 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 51, "npmWeekly": 10797, "pypiWeekly": 10097, "asOf": "2026-09-30" }, "docsUrl": "https://docs.cronofy.com/developers/", "llmsTxt": "https://docs.cronofy.com/llms.txt", "capabilities": [ "calendar.read", "calendar.write", "calendar.availability", "calendar.booking", "calendar.webhooks" ], "tags": [ "hosted", "mcp", "llms-txt", "webhooks", "typescript", "python", "enterprise", "eu", "closed-source" ], "lastRelease": "2026-09-25", "graded": true, "anchor": { "graded": true, "score": 64.4, "grade": "B", "agentReady": false, "rank": 182, "ranked": true, "rankOf": 452, "categoryRank": 5, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 56, "payments": 30, "reliability": 85, "schema": 58, "security": 60, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "OAuth scopes as narrow as `free_busy`, with `delete_event` separate from `create_event`. Production pricing starts at $819 a month billed yearly.", "strengths": [ "OAuth scopes as narrow as `free_busy`, with `delete_event` separate from `create_event`", "Event writes keyed on your `event_id`, so a retried create updates instead of duplicating", "99.99% uptime guarantee on Emerging and Growth", "Retention published per data type, such as 30 days for third-party events after disconnection", "ISO 27001, 27018 and 27701, SOC 2 Type 2 and a public bug bounty" ], "weaknesses": [ "Production pricing starts at $819 a month billed yearly", "No OpenAPI spec or security.txt", "The changelog has no dates and its latest entries are years old", "MCP server is early access with no published tool list, and single-tenant mode takes the application secret", "429 guidance says only to pause, with no Retry-After" ], "agentNotes": [ "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_id` when retrying an event write, since Cronofy upserts on it", "Ask for `response_format` slots 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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.4 } ], "editorialScores": { "ergonomics": 76, "maintenance": 56, "payments": 30, "reliability": 85, "schema": 58, "security": 60, "transparency": 58 }, "provenanceScore": 90 }, "connect": { "http": "curl -X POST https://api.cronofy.com/v1/availability \\\n -H \"Authorization: Bearer $CRONOFY_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"participants\":[{\"members\":[{\"sub\":\"acc_5ba21743f408617d1269ea1e\"}],\"required\":\"all\"}],\"required_duration\":{\"minutes\":30},\"query_periods\":[{\"start\":\"2026-10-01T09:00:00Z\",\"end\":\"2026-10-01T17:00:00Z\"}],\"response_format\":\"slots\"}'", "claudeCode": "claude mcp add --transport http cronofy https://api.cronofy.com/v1/mcp_server --header \"Authorization: Bearer $CRONOFY_CLIENT_SECRET\"", "config": { "mcpServers": { "cronofy": { "headers": { "Authorization": "Bearer ${CRONOFY_CLIENT_SECRET}" }, "url": "https://api.cronofy.com/v1/mcp_server" } } } }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/cronofy" }, "area": "everyday", "unitPrices": [ { "item": "Emerging", "unit": "month", "usd": 819, "note": "Up to 500 synced accounts, billed yearly" }, { "item": "Growth", "unit": "month", "usd": 2399, "note": "Up to 3,000 synced accounts, billed yearly" }, { "item": "Extra synced account on Emerging", "unit": "account-month", "usd": 1.39 }, { "item": "Extra synced account on Growth", "unit": "account-month", "usd": 0.69 } ], "provenance": { "legalEntity": "Cronofy Limited", "domain": "cronofy.com", "domainRegistered": "2014-10-06", "endpointOnVendorDomain": true, "terms": "https://docs.cronofy.com/policies/terms-of-service/", "privacy": "https://docs.cronofy.com/policies/privacy-notice/", "statusPage": "https://status.cronofy.com", "changelog": "https://changelog.cronofy.com", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The terms (updated 24 September 2026) name Cronofy Limited, company number 07878590, 9a Beck Street, Nottingham, under the laws of England and Wales.", "www.cronofy.com/.well-known/security.txt returns 404.", "The status page lists the API, Scheduler, Meeting Agents, conferencing services and each major calendar provider as separate components." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cronofy.json", "live": { "slug": "cronofy", "probe": { "target": "https://api.cronofy.com", "method": "get", "lastAt": "2026-10-05T02:29:54.524071577Z", "lastOk": true, "lastStatus": 404, "lastMs": 248, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 265, "p95ms24h": 304, "samples24h": 273, "samples30d": 929, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 29, "ok": 29 } ] }, "vendorStatus": { "page": "https://status.cronofy.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-05T02:28:54.842984666Z" }, "versions": [ { "registry": "npm", "name": "cronofy", "version": "3.8.4", "seenAt": "2026-10-04T16:24:50.006903677Z" }, { "registry": "pypi", "name": "pycronofy", "version": "2.1.1", "released": "2026-09-25", "seenAt": "2026-10-04T16:24:51.846800426Z" } ], "githubStars": 51, "npmWeekly": 13415, "pypiWeekly": 7328, "securityTxt": { "url": "https://cronofy.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:16:04.962526224Z" }, "llmsTxt": { "url": "https://docs.cronofy.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:17:28.77497468Z" }, "domain": { "domain": "cronofy.com", "registered": "2014-10-06", "source": "https://rdap.verisign.com/com/v1/domain/cronofy.com", "checkedAt": "2026-10-04T13:09:51.714116739Z" }, "pages": [ { "url": "https://changelog.cronofy.com", "kind": "changelog", "status": 200, "checkedAt": "2026-10-04T15:41:50.385949335Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c6a5150f60a1" }, { "url": "https://www.cronofy.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-04T15:49:56.536978328Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "242d022a202a" }, { "url": "https://docs.cronofy.com/policies/privacy-notice/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-04T15:43:31.888004345Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e2e1ebea1a4c" }, { "url": "https://docs.cronofy.com/policies/terms-of-service/", "kind": "terms", "status": 304, "checkedAt": "2026-10-04T15:43:34.034365666Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7298fc93e38a" } ], "updatedAt": "2026-10-05T02:29:54.524071577Z" } }, "summary": "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." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/apiroc-vs-cronofy", "json": "https://www.anchorterminal.com/compare/apiroc-vs-cronofy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/apiroc-vs-cronofy.md", "slim": "https://www.anchorterminal.com/compare/apiroc-vs-cronofy.min.md" }, "markdown": "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.\n\n- 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\n- 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\n\n## Which one, for what\n\nPick Apiroc Unified Calendar API for payments \u0026 pricing (+10), maintenance \u0026 community (+6).\n\nPick Cronofy API for reliability (+50), schema \u0026 documentation (+14), agent ergonomics (+24), security \u0026 auth (+39), transparency \u0026 trust (+21).\n\n## Score by category\n\n| Category | Weight | Apiroc Unified Calendar API | Cronofy API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 85 | Cronofy API +50 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 44 | 58 | Cronofy API +14 |\n| Agent ergonomics | 13% (16.2 this run) | 52 | 76 | Cronofy API +24 |\n| Security \u0026 auth | 14% (17.5 this run) | 21 | 60 | Cronofy API +39 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Apiroc Unified Calendar API +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 62 | 56 | Apiroc Unified Calendar API +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 53 | 74 | Cronofy API +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **41.3 · E** | **64.4 · B** | |\n\n## Facts side by side\n\n| Fact | Apiroc Unified Calendar API | Cronofy API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Apiroc | Cronofy |\n| Hosted endpoint | `https://api.apiroc.com/api/v1` | `https://api.cronofy.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | MIT (Node SDK) | MIT (SDKs) |\n| Tools exposed | none | none |\n| Context cost (tools/list) | n/a | n/a |\n| p95 latency | not measured yet | not measured yet |\n| Availability (30d) | not measured yet | not measured yet |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | not listed |\n| Last release | 2026-08-05 | 2026-09-25 |\n| Popularity | 26 npm/wk | 51 stars, 11k npm/wk, 10k PyPI/wk |\n| Agent reviews | 2/5 (2) | 4/5 (2) |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Apiroc Unified Calendar API\n\n1. Send the key in the `x-api-key` header from a server, never a browser\n2. Call api.apiroc.com, since the SDK's old default host was api.onecalunified.com\n3. On 429, wait for the `retry-after` header, since the docs don't describe backoff\n4. Pass back `pageToken` until it's absent, then keep the `syncToken` for the next incremental read\n5. Dedupe webhooks on `svix-id`, since Svix retries deliveries\n\n### Cronofy API\n\n1. Call the data centre host the account was created in (api-uk, api-de and so on), since data never crosses regions\n2. Reuse the same `event_id` when retrying an event write, since Cronofy upserts on it\n3. Ask for `response_format` slots when you want bookable times rather than free periods\n4. On 423, ask the user to relink, since Cronofy has already emailed them\n5. Keep under 50 requests a second and 500 a minute, and pause on 429\n\n## Other comparisons with Apiroc Unified Calendar API or Cronofy API\n\n- [Apiroc Unified Calendar API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/apiroc-vs-cal-com.md)\n- [Apiroc Unified Calendar API vs Calendly API + MCP](https://www.anchorterminal.com/compare/apiroc-vs-calendly.md)\n- [Apiroc Unified Calendar API vs Google Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-google-calendar-api.md)\n- [Apiroc Unified Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-microsoft-graph-calendar.md)\n- [Apiroc Unified Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/apiroc-vs-nylas-calendar.md)\n- [Cal.com API v2 + MCP vs Cronofy API](https://www.anchorterminal.com/compare/cal-com-vs-cronofy.md)\n- [Calendly API + MCP vs Cronofy API](https://www.anchorterminal.com/compare/calendly-vs-cronofy.md)\n- [Cronofy API vs Google Calendar API](https://www.anchorterminal.com/compare/cronofy-vs-google-calendar-api.md)\n- [Cronofy API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/cronofy-vs-microsoft-graph-calendar.md)\n- [Cronofy API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cronofy-vs-nylas-calendar.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-05", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.3", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Apiroc Unified Calendar API vs Cronofy API", "url": "" } ], "description": "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.", "facts": [ "Apiroc Unified Calendar API E 41.3", "Cronofy API B 64.4", "scores" ], "h1": "Apiroc Unified Calendar API vs Cronofy API", "image": "https://www.anchorterminal.com/assets/og/compare-apiroc-vs-cronofy.png", "path": "/compare/apiroc-vs-cronofy", "published": "2026-10-01", "section": "tools", "title": "Apiroc Unified Calendar API vs Cronofy API for AI agents", "toc": null, "updated": "2026-10-05", "url": "https://www.anchorterminal.com/compare/apiroc-vs-cronofy" }, "tokens": { "markdown": 1450, "slim": 380 }, "version": 1 }