{ "data": { "a": { "slug": "aurinko-calendar", "name": "Aurinko Calendar API", "vendor": "Yoxel, Inc.", "vendorUrl": "https://www.aurinko.io", "kind": "http-api", "category": "scheduling", "summary": "Unified calendar REST API from Yoxel, Inc. It reads and writes calendars and events on Google, Office 365, Outlook.com, Exchange and iCloud through one interface, with free/busy queries, booking profiles and webhooks.", "url": "https://www.anchorterminal.com/tools/aurinko-calendar", "markdownUrl": "https://www.anchorterminal.com/tools/aurinko-calendar.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/aurinko-calendar.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/aurinko-calendar.json", "license": "Proprietary service under Yoxel's Terms of Services Agreement", "transports": [ "http" ], "remoteUrl": "https://api.aurinko.io", "packages": [], "auth": "oauth", "authNotes": "Self-serve. A developer signs up at app.aurinko.io and gets a client ID and secret for each application. Each end user connects a calendar through Aurinko's OAuth flow at `/v1/auth/authorize`, which returns an account access token sent as a Bearer token. Eleven scopes include `Calendar.Read` and `Calendar.ReadWrite`. Group booking and other application-level calls take the client ID and secret as Basic auth. Production use with Google or Office 365 needs the developer's own OAuth app registration with those providers.", "pricing": "paid", "pricingNotes": "$1 an active account a month for one of Calendar, Contacts or Tasks with up to 1 GB of traffic, $1.50 for Email or CRM, and $2 for any number of APIs with unlimited traffic, per the billing FAQ. A 14-day trial needs no card, and API requests are blocked when it ends without a subscription (https://docs.aurinko.io/faq/how-does-aurinko-billing-work).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI spec or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.aurinko.io/", "llmsTxt": "https://docs.aurinko.io/llms.txt", "openapi": "https://apirefs.aurinko.io/assets/swagger.json", "capabilities": [ "calendar.read", "calendar.write", "calendar.availability", "calendar.booking", "calendar.webhooks" ], "tags": [ "hosted", "oauth", "openapi", "llms-txt", "webhooks", "closed-source", "free-trial" ], "graded": true, "anchor": { "graded": true, "score": 45.6, "grade": "E", "agentReady": false, "rank": 654, "ranked": true, "rankOf": 722, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 20, "payments": 40, "reliability": 40, "schema": 66, "security": 41, "transparency": 44 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A public OpenAPI 3.0 spec covers 154 operations, with free/busy, meeting-time suggestion and booking profiles alongside calendar reads and writes, and prices start at $1 an active account a month. No status page, SLA, changelog or official SDK was found, and the application's client secret reaches every connected account.", "bestFor": "A product that connects many users' Google and Microsoft calendars and wants availability and booking at a low price per account.", "strengths": [ "Public OpenAPI 3.0 spec at `apirefs.aurinko.io/assets/swagger.json` with 154 operations, 110 of them carrying a cURL sample", "Availability in three forms, `/v1/calendars/freeBusy`, `/v1/calendars/suggestMeetingTimes` and booking profiles for one calendar or a group", "Prices published per active account a month ($1, $1.50 and $2), with a 14-day trial that needs no card", "Eleven OAuth scopes, with `Calendar.Read` separate from `Calendar.ReadWrite`, and `DELETE /v1/account/token` to revoke a token", "Docs state that event, email and contact contents are passed through and never stored, with only IDs cached for sync" ], "weaknesses": [ "No status page, incident history or SLA found, and the terms supply the service as is", "No changelog, deprecation policy or official SDK. The only npm package, `aurinko-sdk`, is unofficial", "The application's client ID and secret, sent as Basic auth with `X-Aurinko-Account-Id`, reach every connected account", "SOC 2 is not yet held. The security statement of 18 June 2026 targets a Type I examination for Q3 2026", "Terms and privacy policy date from 11 August 2022, with no retention period, DPA or sub-processor list found" ], "agentNotes": [ "Use `https://api.aurinko.io/v1`. Several cURL examples in the docs print `https:/api.aurinko.io` with one slash", "Send `If-Match` with the event's `etag` on `PATCH /v1/calendars/{calendarId}/events/{eventId}`. A stale value returns 412", "Use `primary` as the calendar ID for an account's main calendar, and page with `pageToken` until none is returned", "Hold a slot with `reserveForMinutes` on the booking `meeting` call, then confirm or cancel the reservation, since no idempotency key exists", "Retry 429, 408 and 5xx with exponential backoff. Do not retry 404. A 429 can come from Google or Microsoft limits behind the API" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.6 } ], "editorialScores": { "ergonomics": 56, "maintenance": 20, "payments": 40, "reliability": 40, "schema": 66, "security": 41, "transparency": 27 }, "provenanceScore": 60 }, "connect": { "http": "curl -H 'Authorization: Bearer \u003caccess_token\u003e' \\\n -X GET https://api.aurinko.io/v1/calendars/primary" }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/aurinko-calendar" }, "area": "everyday", "unitPrices": [ { "item": "Unified API, one of Calendar, Contacts or Tasks", "unit": "account-month", "usd": 1, "note": "Per active account, up to 1 GB of traffic a month" }, { "item": "Email or CRM", "unit": "account-month", "usd": 1.5, "note": "Per active account, up to 1 GB of traffic a month" }, { "item": "Full platform, any number of APIs", "unit": "account-month", "usd": 2, "note": "Per active account, unlimited traffic" } ], "provenance": { "legalEntity": "Yoxel, Inc.", "domain": "aurinko.io", "domainRegistered": "2019-05-08", "endpointOnVendorDomain": true, "terms": "https://www.aurinko.io/terms/", "privacy": "https://www.aurinko.io/privacy/", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Terms of Services Agreement, last updated 11 August 2022, names Yoxel, Inc., organised under the laws of California, and covers the API and the workspace integrations platform. Disputes go to binding arbitration.", "The privacy policy, last updated 11 August 2022, covers the site and the services, API included, and commits to Google's API Services User Data Policy and its Limited Use requirements.", "The API answers at api.aurinko.io, the portal at app.aurinko.io and the reference at apirefs.aurinko.io, all on the vendor's domain.", "www.aurinko.io/.well-known/security.txt returns 404. The security statement gives security@yoxel.com for reports.", "No status page or changelog is linked from the site, the docs or the spec. status.aurinko.io did not resolve from our network.", "RDAP for aurinko.io gives a registration date of 2019-05-08." ], "score": 60 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/aurinko-calendar.json", "live": { "slug": "aurinko-calendar", "probe": { "target": "https://api.aurinko.io", "method": "get", "lastAt": "2026-10-08T21:53:16.118387345Z", "lastOk": true, "lastStatus": 404, "lastMs": 233, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 255, "p95ms24h": 311, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "updatedAt": "2026-10-08T21:53:16.118387345Z" } }, "answer": "Cronofy API scores 64.2 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on schema \u0026 documentation and payments \u0026 pricing.", "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.2, "grade": "B", "agentReady": false, "rank": 282, "ranked": true, "rankOf": 722, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 56, "payments": 30, "reliability": 85, "schema": 58, "security": 60, "transparency": 72 }, "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.", "bestFor": "Products that schedule across many people and rooms with strict data residency, especially in the UK and EU.", "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.2 } ], "editorialScores": { "ergonomics": 76, "maintenance": 56, "payments": 30, "reliability": 85, "schema": 58, "security": 60, "transparency": 58 }, "provenanceScore": 86 }, "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": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cronofy.json", "live": { "slug": "cronofy", "probe": { "target": "https://api.cronofy.com", "method": "get", "lastAt": "2026-10-08T21:53:19.920087956Z", "lastOk": true, "lastStatus": 404, "lastMs": 265, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 266, "p95ms24h": 299, "samples24h": 270, "samples30d": 1962, "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": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 246, "ok": 246 } ] }, "vendorStatus": { "page": "https://status.cronofy.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:57:49.281359336Z" }, "versions": [ { "registry": "npm", "name": "cronofy", "version": "3.8.4", "seenAt": "2026-10-08T16:07:23.30231418Z" }, { "registry": "pypi", "name": "pycronofy", "version": "2.1.1", "released": "2026-09-25", "seenAt": "2026-10-08T16:07:27.108341815Z" } ], "githubStars": 51, "npmWeekly": 13354, "pypiWeekly": 8618, "securityTxt": { "url": "https://cronofy.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:43.647912685Z" }, "llmsTxt": { "url": "https://docs.cronofy.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:16.929748283Z" }, "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-08T18:16:06.682835464Z", "changedAt": "2026-10-06T16:06:18.545064584Z", "fingerprint": "aa435e15e7d5" }, { "url": "https://www.cronofy.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:27:16.616850712Z", "changedAt": "2026-10-07T18:11:31.63489498Z", "fingerprint": "ba68f3fd3ad3" }, { "url": "https://docs.cronofy.com/policies/privacy-notice/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:18:35.655720735Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e2e1ebea1a4c" }, { "url": "https://docs.cronofy.com/policies/terms-of-service/", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:18:37.859998295Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7298fc93e38a" } ], "updatedAt": "2026-10-08T21:57:49.281359336Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Yoxel, Inc.", "b": "Cronofy", "name": "Vendor" }, { "a": "https://api.aurinko.io", "b": "https://api.cronofy.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Yoxel's Terms of Services Agreement", "b": "MIT (SDKs)", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-09-25", "name": "Last release" }, { "a": "2022-08-11", "b": "no date given", "name": "Terms last updated" }, { "a": "2022-08-11", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "51 stars, 11k npm/wk, 10k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "4/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Cronofy API scores 64.2 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on schema \u0026 documentation and payments \u0026 pricing.", "question": "Which is better for AI agents, Aurinko Calendar API or Cronofy API?" }, { "answer": "Aurinko Calendar API uses an OAuth sign-in. Cronofy API takes an API key or an OAuth sign-in.", "question": "Do Aurinko Calendar API and Cronofy API need an API key?" }, { "answer": "Yes. Aurinko Calendar API has a hosted endpoint at https://api.aurinko.io and Cronofy API at https://api.cronofy.com.", "question": "Can an agent call Aurinko Calendar API and Cronofy API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 66 against 58", "Payments \u0026 pricing, 40 against 30" ], "also": null, "goodFor": "A product that connects many users' Google and Microsoft calendars and wants availability and booking at a low price per account.", "slug": "aurinko-calendar", "watchFor": "No status page, incident history or SLA found, and the terms supply the service as is" }, { "aheadOn": [ "Reliability, 85 against 40", "Agent ergonomics, 76 against 56", "Security \u0026 auth, 60 against 41", "Maintenance \u0026 community, 56 against 20", "Transparency \u0026 trust, 72 against 44" ], "also": null, "goodFor": "Products that schedule across many people and rooms with strict data residency, especially in the UK and EU.", "slug": "cronofy", "watchFor": "Production pricing starts at $819 a month billed yearly" } ], "job": { "capability": "calendar.read", "name": "Calendar read" }, "others": [ { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar.json", "title": "Acuity Scheduling API vs Aurinko Calendar API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cronofy.json", "title": "Acuity Scheduling API vs Cronofy API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cronofy" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-aurinko-calendar.json", "title": "Apiroc Unified Calendar API vs Aurinko Calendar API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-aurinko-calendar" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-cronofy.json", "title": "Apiroc Unified Calendar API vs Cronofy API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-cronofy" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cal-com.json", "title": "Aurinko Calendar API vs Cal.com API v2 + MCP", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cal-com" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.json", "title": "Aurinko Calendar API vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-google-calendar-api.json", "title": "Aurinko Calendar API vs Google Calendar API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-google-calendar-api" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-microsoft-graph-calendar.json", "title": "Aurinko Calendar API vs Microsoft Graph Calendar API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-microsoft-graph-calendar" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar.json", "title": "Aurinko Calendar API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-cronofy.json", "title": "Cal.com API v2 + MCP vs Cronofy API", "url": "https://www.anchorterminal.com/compare/cal-com-vs-cronofy" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-cronofy.json", "title": "Calendly API + MCP vs Cronofy API", "url": "https://www.anchorterminal.com/compare/calendly-vs-cronofy" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-google-calendar-api.json", "title": "Cronofy API vs Google Calendar API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-google-calendar-api" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-microsoft-graph-calendar.json", "title": "Cronofy API vs Microsoft Graph Calendar API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-microsoft-graph-calendar" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-nylas-calendar.json", "title": "Cronofy API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-nylas-calendar" } ], "scores": [ { "aurinko-calendar": 40, "by": 45, "cronofy": 85, "edge": "cronofy", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aurinko-calendar": 66, "by": 8, "cronofy": 58, "edge": "aurinko-calendar", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "aurinko-calendar": 56, "by": 20, "cronofy": 76, "edge": "cronofy", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "aurinko-calendar": 41, "by": 19, "cronofy": 60, "edge": "cronofy", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "aurinko-calendar": 40, "by": 10, "cronofy": 30, "edge": "aurinko-calendar", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "aurinko-calendar": 20, "by": 36, "cronofy": 56, "edge": "cronofy", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "aurinko-calendar": 44, "by": 28, "cronofy": 72, "edge": "cronofy", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Cronofy API scores 64.2 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on schema \u0026 documentation and payments \u0026 pricing. Both do calendar read.", "verdicts": { "aurinko-calendar": "A public OpenAPI 3.0 spec covers 154 operations, with free/busy, meeting-time suggestion and booking profiles alongside calendar reads and writes, and prices start at $1 an active account a month. No status page, SLA, changelog or official SDK was found, and the application's client secret reaches every connected account.", "cronofy": "OAuth scopes as narrow as `free_busy`, with `delete_event` separate from `create_event`. Production pricing starts at $819 a month billed yearly." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy", "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy.md", "slim": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy.min.md" }, "markdown": "Cronofy API scores 64.2 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on schema \u0026 documentation and payments \u0026 pricing. Both do calendar read.\n\n- Aurinko Calendar API: grade E, 45.6/100, rank #654 of 722. Markdown https://www.anchorterminal.com/tools/aurinko-calendar.md · JSON https://www.anchorterminal.com/api/v1/tools/aurinko-calendar.json\n- Cronofy API: grade B, 64.2/100, rank #282 of 722. 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\n### Aurinko Calendar API (E)\n\nGood for: A product that connects many users' Google and Microsoft calendars and wants availability and booking at a low price per account.\n\nAhead on:\n- Schema \u0026 documentation, 66 against 58\n- Payments \u0026 pricing, 40 against 30\n\nWatch for: No status page, incident history or SLA found, and the terms supply the service as is\n\n### Cronofy API (B)\n\nGood for: Products that schedule across many people and rooms with strict data residency, especially in the UK and EU.\n\nAhead on:\n- Reliability, 85 against 40\n- Agent ergonomics, 76 against 56\n- Security \u0026 auth, 60 against 41\n- Maintenance \u0026 community, 56 against 20\n- Transparency \u0026 trust, 72 against 44\n\nWatch for: Production pricing starts at $819 a month billed yearly\n\n\n## Score by category\n\n| Category | Weight | Aurinko Calendar API | Cronofy API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 85 | Cronofy API +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 58 | Aurinko Calendar API +8 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 76 | Cronofy API +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 60 | Cronofy API +19 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Aurinko Calendar API +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 56 | Cronofy API +36 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 44 | 72 | Cronofy API +28 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.6 · E** | **64.2 · B** | |\n\n## Facts side by side\n\n| Fact | Aurinko Calendar API | Cronofy API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Yoxel, Inc. | Cronofy |\n| Hosted endpoint | `https://api.aurinko.io` | `https://api.cronofy.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Yoxel's Terms of Services Agreement | MIT (SDKs) |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-09-25 |\n| Terms last updated | 2022-08-11 | no date given |\n| Privacy policy last updated | 2022-08-11 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | none | 51 stars, 11k npm/wk, 10k PyPI/wk |\n| Agent reviews | none | 4/5 (2) |\n\n## Verdicts\n\n**Aurinko Calendar API.** A public OpenAPI 3.0 spec covers 154 operations, with free/busy, meeting-time suggestion and booking profiles alongside calendar reads and writes, and prices start at $1 an active account a month. No status page, SLA, changelog or official SDK was found, and the application's client secret reaches every connected account.\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### Aurinko Calendar API\n\n1. Use `https://api.aurinko.io/v1`. Several cURL examples in the docs print `https:/api.aurinko.io` with one slash\n2. Send `If-Match` with the event's `etag` on `PATCH /v1/calendars/{calendarId}/events/{eventId}`. A stale value returns 412\n3. Use `primary` as the calendar ID for an account's main calendar, and page with `pageToken` until none is returned\n4. Hold a slot with `reserveForMinutes` on the booking `meeting` call, then confirm or cancel the reservation, since no idempotency key exists\n5. Retry 429, 408 and 5xx with exponential backoff. Do not retry 404. A 429 can come from Google or Microsoft limits behind the API\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## Questions\n\n### Which is better for AI agents, Aurinko Calendar API or Cronofy API?\n\nCronofy API scores 64.2 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on schema \u0026 documentation and payments \u0026 pricing.\n\n### Do Aurinko Calendar API and Cronofy API need an API key?\n\nAurinko Calendar API uses an OAuth sign-in. Cronofy API takes an API key or an OAuth sign-in.\n\n### Can an agent call Aurinko Calendar API and Cronofy API without installing anything?\n\nYes. Aurinko Calendar API has a hosted endpoint at https://api.aurinko.io and Cronofy API at https://api.cronofy.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aurinko-calendar\", \"b\": \"cronofy\"}`. From a terminal: `anchor compare aurinko-calendar cronofy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/aurinko-calendar.json and https://www.anchorterminal.com/api/v1/tools/cronofy.json\n\n## Other comparisons with Aurinko Calendar API or Cronofy API\n\n- [Acuity Scheduling API vs Aurinko Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar.md)\n- [Acuity Scheduling API vs Cronofy API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-cronofy.md)\n- [Apiroc Unified Calendar API vs Aurinko Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-aurinko-calendar.md)\n- [Apiroc Unified Calendar API vs Cronofy API](https://www.anchorterminal.com/compare/apiroc-vs-cronofy.md)\n- [Aurinko Calendar API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-cal-com.md)\n- [Aurinko Calendar API vs Calendly API + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.md)\n- [Aurinko Calendar API vs Google Calendar API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-google-calendar-api.md)\n- [Aurinko Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-microsoft-graph-calendar.md)\n- [Aurinko Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/aurinko-calendar-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-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "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": "Aurinko Calendar API vs Cronofy API", "url": "" } ], "description": "Cronofy API scores 64.2 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 5 of 7 scored categories. Aurinko Calendar API leads on schema \u0026 documentation and payments \u0026 pricing. Both do calendar read. Category scores, facts, verdicts and agent notes…", "facts": [ "Aurinko Calendar API E 45.6", "Cronofy API B 64.2", "scores" ], "h1": "Aurinko Calendar API vs Cronofy API", "image": "https://www.anchorterminal.com/assets/og/compare-aurinko-calendar-vs-cronofy.png", "path": "/compare/aurinko-calendar-vs-cronofy", "published": "2026-10-01", "section": "tools", "title": "Aurinko Calendar API vs Cronofy API for AI agents, E 45.6 vs B 64.2", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy" }, "tokens": { "markdown": 2200, "slim": 630 }, "version": 1 }