{ "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": "Calendly API + MCP scores 68.3 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Aurinko Calendar API leads on payments \u0026 pricing.", "b": { "slug": "calendly", "name": "Calendly API + MCP", "vendor": "Calendly", "vendorUrl": "https://calendly.com", "kind": "http-api", "category": "scheduling", "summary": "Calendly's scheduling API for availability, bookings, invitees and webhooks, with a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/calendly", "markdownUrl": "https://www.anchorterminal.com/tools/calendly.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/calendly.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/calendly.json", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.calendly.com", "packages": [], "auth": "mixed", "authNotes": "Personal access tokens for your own account, OAuth apps for other people's. Both go in the `Authorization: Bearer` header. The hosted MCP uses OAuth 2.1 with PKCE and dynamic client registration only. Only 8 OAuth tokens per user can be requested in a minute.", "pricing": "freemium", "pricingNotes": "Free plan. The pricing page lists Standard at $10 a seat a month and Teams at $16, and says yearly billing saves 17 and 20 per cent. Enterprise starts at $15,000 a year with a 50-seat minimum, in USD only (https://calendly.com/pricing). Booking through the API needs Standard or above (https://developer.calendly.com/api-docs/calendly-api/scheduled-events/create-event-invitee.md).", "priceSummary": "$10 / seat-mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 36, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://developer.calendly.com", "llmsTxt": "https://developer.calendly.com/llms.txt", "openapi": "https://developer.calendly.com/openapi.json", "capabilities": [ "calendar.read", "calendar.availability", "calendar.booking", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "mcp", "llms-txt", "openapi", "webhooks", "oauth", "closed-source", "enterprise" ], "lastRelease": "2026-08-25", "graded": true, "anchor": { "graded": true, "score": 68.3, "grade": "B", "agentReady": false, "rank": 182, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 61, "maintenance": 50, "payments": 30, "reliability": 85, "schema": 86, "security": 70, "transparency": 80 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP. Booking through the API needs a paid seat, and Free users get a 403.", "bestFor": "Best when the host already schedules through Calendly and the agent needs to find a slot and book or cancel it.", "strengths": [ "Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP", "MCP tools annotated with readOnlyHint, destructiveHint and idempotentHint", "OpenAPI 3.1 in JSON and YAML, llms.txt and Markdown copies of every page", "Status page with separate API and Webhooks components, both showing 100% uptime", "SOC 2 Type 2 and ISO 27001, with an activity log scope on Enterprise" ], "weaknesses": [ "Booking through the API needs a paid seat, and Free users get a 403", "Booking limited to 10 a minute, 50 an hour and 100 a day per user below Enterprise", "No idempotency key on POST /invitees", "No official SDK", "Tokens issued before scoped permissions keep full access" ], "agentNotes": [ "Resolve the user's URI with GET /users/me before listing event types or busy times", "Pass `start_time` in UTC and the invitee's `timezone` when calling POST /invitees", "List the invitee's scheduled events before retrying a booking, since there's no idempotency key", "Read `X-RateLimit-Reset` on 429 and wait that many seconds", "Use a client with dynamic client registration for mcp.calendly.com, since it has no static client ID" ], "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": 68.3 } ], "editorialScores": { "ergonomics": 61, "maintenance": 50, "payments": 30, "reliability": 85, "schema": 86, "security": 70, "transparency": 61 }, "provenanceScore": 99 }, "connect": { "http": "curl https://api.calendly.com/users/me -H \"Authorization: Bearer $CALENDLY_TOKEN\"", "claudeCode": "claude mcp add --transport http calendly https://mcp.calendly.com", "config": { "mcpServers": { "calendly": { "url": "https://mcp.calendly.com" } } } }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/calendly" }, "area": "everyday", "unitPrices": [ { "item": "Standard", "unit": "seat-month", "usd": 10, "note": "Headline price on the pricing page, which toggles yearly and monthly billing" }, { "item": "Teams", "unit": "seat-month", "usd": 16, "note": "Headline price on the pricing page, which toggles yearly and monthly billing" } ], "provenance": { "legalEntity": "Calendly, LLC", "domain": "calendly.com", "domainRegistered": "2013-02-26", "endpointOnVendorDomain": true, "terms": "https://calendly.com/legal/customer-terms-conditions", "privacy": "https://calendly.com/legal/privacy-notice", "statusPage": "https://www.calendlystatus.com", "changelog": "https://developer.calendly.com/release-notes", "securityTxt": "valid", "checked": "2026-09-30", "notes": [ "The privacy notice (updated 3 July 2026) names Calendly, LLC and a postal address in Buford, Georgia, and lists EEA and UK representatives.", "security.txt lists security@calendly.com and expires 2027-04-10.", "A developer policy sits at calendly.com/legal/developer-policy alongside the customer terms." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/calendly.json", "live": { "slug": "calendly", "probe": { "target": "https://api.calendly.com", "method": "get", "lastAt": "2026-10-08T21:53:18.717889709Z", "lastOk": true, "lastStatus": 401, "lastMs": 122, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 125, "p95ms24h": 171, "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://www.calendlystatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:57:44.529489865Z" }, "securityTxt": { "url": "https://calendly.com/.well-known/security.txt", "state": "valid", "expires": "2027-04-10T00:00:00.000Z", "checkedAt": "2026-10-08T15:38:50.46154565Z" }, "llmsTxt": { "url": "https://developer.calendly.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:10.051340817Z" }, "domain": { "domain": "calendly.com", "registered": "2013-02-26", "source": "https://rdap.verisign.com/com/v1/domain/calendly.com", "checkedAt": "2026-10-04T13:07:34.738480938Z" }, "pages": [ { "url": "https://developer.calendly.com/release-notes", "kind": "changelog", "status": 304, "checkedAt": "2026-10-08T18:17:08.101348382Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6b8c2bf3ffd2" }, { "url": "https://calendly.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:16:04.151613781Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d5a9d70a2911" }, { "url": "https://calendly.com/legal/privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:16:02.119008526Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "881ce0a81fb2" }, { "url": "https://calendly.com/legal/customer-terms-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:15:59.792926327Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b8ae1bf79b38" } ], "updatedAt": "2026-10-08T21:57:44.529489865Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Yoxel, Inc.", "b": "Calendly", "name": "Vendor" }, { "a": "https://api.aurinko.io", "b": "https://api.calendly.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Yoxel's Terms of Services Agreement", "b": "none", "name": "Licence" }, { "a": "none", "b": "36", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-08-25", "name": "Last release" }, { "a": "2022-08-11", "b": "2026-08-05", "name": "Terms last updated" }, { "a": "2022-08-11", "b": "2026-07-03", "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": "not found in the text", "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": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "4/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Calendly API + MCP scores 68.3 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Aurinko Calendar API leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Aurinko Calendar API or Calendly API + MCP?" }, { "answer": "Aurinko Calendar API uses an OAuth sign-in. Calendly API + MCP takes an API key or an OAuth sign-in.", "question": "Do Aurinko Calendar API and Calendly API + MCP need an API key?" }, { "answer": "Yes. Aurinko Calendar API has a hosted endpoint at https://api.aurinko.io and Calendly API + MCP at https://api.calendly.com.", "question": "Can an agent call Aurinko Calendar API and Calendly API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "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", "Schema \u0026 documentation, 86 against 66", "Agent ergonomics, 61 against 56", "Security \u0026 auth, 70 against 41", "Maintenance \u0026 community, 50 against 20", "Transparency \u0026 trust, 80 against 44" ], "also": null, "goodFor": "Best when the host already schedules through Calendly and the agent needs to find a slot and book or cancel it.", "slug": "calendly", "watchFor": "Booking through the API needs a paid seat, and Free users get a 403" } ], "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-calendly.json", "title": "Acuity Scheduling API vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-calendly" }, { "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-calendly.json", "title": "Apiroc Unified Calendar API vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/apiroc-vs-calendly" }, { "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-cronofy.json", "title": "Aurinko Calendar API vs Cronofy API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy" }, { "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-calendly.json", "title": "Cal.com API v2 + MCP vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/cal-com-vs-calendly" }, { "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/calendly-vs-google-calendar-api.json", "title": "Calendly API + MCP vs Google Calendar API", "url": "https://www.anchorterminal.com/compare/calendly-vs-google-calendar-api" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-microsoft-graph-calendar.json", "title": "Calendly API + MCP vs Microsoft Graph Calendar API", "url": "https://www.anchorterminal.com/compare/calendly-vs-microsoft-graph-calendar" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar.json", "title": "Calendly API + MCP vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar" } ], "scores": [ { "aurinko-calendar": 40, "by": 45, "calendly": 85, "edge": "calendly", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aurinko-calendar": 66, "by": 20, "calendly": 86, "edge": "calendly", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "aurinko-calendar": 56, "by": 5, "calendly": 61, "edge": "calendly", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "aurinko-calendar": 41, "by": 29, "calendly": 70, "edge": "calendly", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "aurinko-calendar": 40, "by": 10, "calendly": 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": 30, "calendly": 50, "edge": "calendly", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "aurinko-calendar": 44, "by": 36, "calendly": 80, "edge": "calendly", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Calendly API + MCP scores 68.3 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Aurinko Calendar API leads on 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.", "calendly": "Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP. Booking through the API needs a paid seat, and Free users get a 403." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly", "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.md", "slim": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.min.md" }, "markdown": "Calendly API + MCP scores 68.3 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Aurinko Calendar API leads on 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- Calendly API + MCP: grade B, 68.3/100, rank #182 of 722. Markdown https://www.anchorterminal.com/tools/calendly.md · JSON https://www.anchorterminal.com/api/v1/tools/calendly.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- 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### Calendly API + MCP (B)\n\nGood for: Best when the host already schedules through Calendly and the agent needs to find a slot and book or cancel it.\n\nAhead on:\n- Reliability, 85 against 40\n- Schema \u0026 documentation, 86 against 66\n- Agent ergonomics, 61 against 56\n- Security \u0026 auth, 70 against 41\n- Maintenance \u0026 community, 50 against 20\n- Transparency \u0026 trust, 80 against 44\n\nWatch for: Booking through the API needs a paid seat, and Free users get a 403\n\n\n## Score by category\n\n| Category | Weight | Aurinko Calendar API | Calendly API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 85 | Calendly API + MCP +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 86 | Calendly API + MCP +20 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 61 | Calendly API + MCP +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 70 | Calendly API + MCP +29 |\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 | 50 | Calendly API + MCP +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 44 | 80 | Calendly API + MCP +36 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.6 · E** | **68.3 · B** | |\n\n## Facts side by side\n\n| Fact | Aurinko Calendar API | Calendly API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Yoxel, Inc. | Calendly |\n| Hosted endpoint | `https://api.aurinko.io` | `https://api.calendly.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Yoxel's Terms of Services Agreement | none |\n| Tools exposed | none | 36 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-08-25 |\n| Terms last updated | 2022-08-11 | 2026-08-05 |\n| Privacy policy last updated | 2022-08-11 | 2026-07-03 |\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 | not found in the text |\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 | yes |\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**Calendly API + MCP.** Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP. Booking through the API needs a paid seat, and Free users get a 403.\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### Calendly API + MCP\n\n1. Resolve the user's URI with GET /users/me before listing event types or busy times\n2. Pass `start_time` in UTC and the invitee's `timezone` when calling POST /invitees\n3. List the invitee's scheduled events before retrying a booking, since there's no idempotency key\n4. Read `X-RateLimit-Reset` on 429 and wait that many seconds\n5. Use a client with dynamic client registration for mcp.calendly.com, since it has no static client ID\n\n## Questions\n\n### Which is better for AI agents, Aurinko Calendar API or Calendly API + MCP?\n\nCalendly API + MCP scores 68.3 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Aurinko Calendar API leads on payments \u0026 pricing.\n\n### Do Aurinko Calendar API and Calendly API + MCP need an API key?\n\nAurinko Calendar API uses an OAuth sign-in. Calendly API + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Aurinko Calendar API and Calendly API + MCP without installing anything?\n\nYes. Aurinko Calendar API has a hosted endpoint at https://api.aurinko.io and Calendly API + MCP at https://api.calendly.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aurinko-calendar\", \"b\": \"calendly\"}`. From a terminal: `anchor compare aurinko-calendar calendly`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/aurinko-calendar.json and https://www.anchorterminal.com/api/v1/tools/calendly.json\n\n## Other comparisons with Aurinko Calendar API or Calendly API + MCP\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 Calendly API + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-calendly.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 Calendly API + MCP](https://www.anchorterminal.com/compare/apiroc-vs-calendly.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 Cronofy API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-cronofy.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 Calendly API + MCP](https://www.anchorterminal.com/compare/cal-com-vs-calendly.md)\n- [Calendly API + MCP vs Cronofy API](https://www.anchorterminal.com/compare/calendly-vs-cronofy.md)\n- [Calendly API + MCP vs Google Calendar API](https://www.anchorterminal.com/compare/calendly-vs-google-calendar-api.md)\n- [Calendly API + MCP vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/calendly-vs-microsoft-graph-calendar.md)\n- [Calendly API + MCP vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/calendly-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 Calendly API + MCP", "url": "" } ], "description": "Calendly API + MCP scores 68.3 (B) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 6 of 7 scored categories. Aurinko Calendar API leads on payments \u0026 pricing. Both do calendar read. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Aurinko Calendar API E 45.6", "Calendly API + MCP B 68.3", "scores" ], "h1": "Aurinko Calendar API vs Calendly API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-aurinko-calendar-vs-calendly.png", "path": "/compare/aurinko-calendar-vs-calendly", "published": "2026-10-01", "section": "tools", "title": "Aurinko Calendar API vs Calendly API + MCP for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly" }, "tokens": { "markdown": 2200, "slim": 630 }, "version": 1 }