Head to head · Calendar access · October 2026 research run

Apiroc Unified Calendar API vs Calendly API + MCP

Calendly API + MCP scores 71 (BB) on agent readiness against Apiroc Unified Calendar API's 41.9 (E), and leads in 6 of 7 scored categories. Apiroc Unified Calendar API leads on payments & pricing. Both do calendar access.

Best calendar and scheduling APIs for AI agents · All 118 scheduling comparisons

Which one, for what

Apiroc Unified Calendar API E

Best for A small product or an agent builder that needs read and write across Google, Microsoft and iCloud for tens to hundreds of accounts on a tight budget.

Ahead on

  • Payments & pricing, 60 against 45

Also in its favour

  • Free to start without a card

Watch for

No status page history, changelog, OpenAPI spec, llms.txt or security.txt

Calendly API + MCP BB

Best for Best when the host already schedules through Calendly and the agent needs to find a slot and book or cancel it.

Ahead on

  • Reliability, 85 against 35
  • Schema & documentation, 86 against 44
  • Agent ergonomics, 61 against 52
  • Security & auth, 70 against 21
  • Maintenance & community, 60 against 42
  • Transparency & trust, 80 against 51

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 4.0 against 2.0 out of 5

Watch for

Booking through the API needs a paid seat, and Free users get a 403

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Calendly API + MCP +50

Apiroc Unified Calendar API 35

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. No public status page with history. status.apiroc.com doesn't resolve and the homepage shows only an "All systems operational" badge with a claim of 34B+ API calls (0). No readable incident history (5). Rate limits published with numbers, 20 requests a second in Sandbox and 300 in Production per application, plus 600 a minute per Google account and 1,000 a minute per Microsoft account (15). The docs don't mention 429 or Retry-After, though the official Node SDK reads a retry-after header on 429, and webhook docs say to dedupe on svix-id (5). The terms say availability can't be guaranteed, and no SLA was found on any plan (0). GA, with production use licensed on Pro (10). The 429 line's 5 is an in-between value kept from 1 October (the SDK reads retry-after, the docs say nothing). 0 + 5 + 15 + 5 + 0 + 10 = 35.

Calendly API + MCP 85

incident.io status page with separate Calendly API and Webhooks components, plus each calendar provider (20). The page shows 100% uptime for the API and Webhooks components from August to November 2026, and its RSS feed, read on 1 November 2026, lists one completed maintenance window (6 September) and no incidents, so a clean record (30). 500 requests a minute per user on paid plans, 50 on Free, and booking capped at 10 a minute, 50 an hour and 100 a day below Enterprise (15). 429 with X-RateLimit-Limit, -Remaining and -Reset headers and exponential backoff advice, but no idempotency key or safe-retry guidance for booking writes (10). No SLA found on any plan (0). API v2 is GA (10).

Security & auth Calendly API + MCP +49

Apiroc Unified Calendar API 21

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. Your application calls with one x-api-key that reaches every connected end-user account, and we found no key scopes or rotation docs (10). Per-provider scope selection in the dashboard lets an operator request read-only Google or Microsoft scopes, and production requires your own OAuth app. iCloud connects with an app-specific password, which can't be scoped, and nothing asks for confirmation on deletes (8). Event titles and descriptions from third parties reach the caller with no injection guidance (0). Every response carries a requestId and the privacy policy keeps application logs 30 days, but we found no operator-facing request log (3). No security.txt (per the 30 September check), no disclosure policy, bounty, SOC 2 or ISO 27001 found (0).

Calendly API + MCP 70

OAuth 2.1 with PKCE and dynamic client registration on the MCP, and per-resource scopes such as scheduled_events:read and availability:write for new OAuth apps and new personal access tokens since March 2026. Tokens issued before scopes keep full access (28). Read scopes, mcp:scheduling:read and mcp:scheduling:write for the MCP, and destructiveHint on cancel, delete and revoke tools, but no confirmation step of its own (15). Invitee names and booking answers written by outsiders reach the model, with no injection guidance found (0). activity_log:read and audit logs on Enterprise (10). SOC 2 Type 2, ISO 27001, CSA STAR, an annual penetration test and a valid security.txt. No public bug bounty found (17).

Schema & documentation Calendly API + MCP +42

Apiroc Unified Calendar API 44

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. No OpenAPI spec. A Postman collection is the only machine-readable contract (10). No llms.txt, per the 30 September check (0). Reference pages for five resources with parameters and cURL, TypeScript and Python examples, but little on when to use one endpoint over another (10). Typed inputs in the Node SDK and required fields marked in the docs (10). Examples throughout, and an errors page that gives only the shape (error, message, requestId) and the 2xx, 4xx and 5xx ranges, with no list of error names (9). /v1 in the path but no changelog (5).

Calendly API + MCP 86

OpenAPI 3.1 for the scheduling API and a separate one for OAuth, in JSON and YAML (25). llms.txt with about 130 links and Markdown copies of every docs page (10). Reference pages and MCP tool docs mark plan requirements such as paid plan for booking and Teams for routing forms (14). Typed parameters in the spec (12). 400, 401, 403, 404, 409, 424 and 500 responses in the spec. 429 appears on 9 of 65 operations, the contacts endpoints, on 1 November 2026 (12). Dated release notes, latest 30 October 2026. The API version only changes by migration, the last one being v1 to v2 (13).

Transparency & trust Calendly API + MCP +29

Apiroc Unified Calendar API 51

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. Closed service with terms under Albanian law and an MIT Node SDK (15). Privacy policy (24 August 2026) says event content isn't stored persistently, application logs and analytics are kept 30 days, data isn't used to train models, and Google's Limited Use rules apply. A DPA is published. Webhooks are delivered through Svix, which isn't on the sub-processor list, and webhook message retention has no period (18). 30 days' notice for price rises and sub-processor changes, but no API deprecation policy (3). Five sub-processors listed with locations, and servers stated as US. Svix missing (15).

Calendly API + MCP 80

Closed service with customer terms and a separate developer policy (15). Privacy notice (3 July 2026) gives no retention periods, and the no-AI-training statement sits on the security page, not in the privacy notice (18). The v1 to v2 migration notice is dated 26 March 2025 and legacy token behaviour under scopes is written down (12). Sub-processor list linked from the privacy notice, which says data sits in the US or wherever providers operate. We didn't open the list (16).

Maintenance & community Calendly API + MCP +18

Apiroc Unified Calendar API 42

Node SDK v2.1.0, tagged on 8 October 2026 ("feat: add caldav support", connecting any CalDAV server), 33 days before this check (20). From 12 August only that one release; v1.2.2 (14 July) and v1.3.0, v2.0.0 and v2.0.1 (5 August) are now outside the 90 days, and no changelog or other dated source of Apiroc's could be read (0; was 20). No public changelog. Support by email, with priority support on Pro and a Slack channel on Enterprise, per the 1 October check (4). One current official SDK, in Node (10). CI typechecks, lints, builds and tests on pull requests, a tag-triggered workflow publishes to npm, and dependencies were last bumped in May 2026 (8). 20 + 0 + 4 + 10 + 8 = 42.

Calendly API + MCP 60

Latest release note on 30 October 2026 (Teams API), two days before this check (30). Four dated entries since 3 August (25 August, 22, 23 and 30 October) (20). Public release notes and a developer support route, no public issue tracker (10). No official SDKs (0). No package to assess (0).

Payments & pricing Apiroc Unified Calendar API +15

Apiroc Unified Calendar API 60

Per the 1 October check, not re-read on 10 November, because Apiroc's Terms of Service (24 August 2026) bar access to the Site or the Service, docs.apiroc.com included, through a bot, script or other automated means. No x402, MPP or L402 (0). Plan prices and $0.50 per extra end-user account a month published without login (20). Free plan for 10 end-user accounts with no card (20). Browser signup and a dashboard key, no autonomous route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Calendly API + MCP 45

No x402, MPP or L402 (0). Seat prices public ($10 and $16 a seat a month, Enterprise from $15,000 a year) but nothing per call (10). Free plan with API read access and no card, though booking through the API needs a paid seat (20). A person signs up and consents in a browser, even though MCP clients register themselves (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Score by category

CategoryWeightApiroc Unified Calendar APICalendly API + MCPEdge
Reliability16%3585Calendly API + MCP +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4486Calendly API + MCP +42
Agent ergonomics13%5261Calendly API + MCP +9
Security & auth14%2170Calendly API + MCP +49
Payments & pricing10%6045Apiroc Unified Calendar API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4260Calendly API + MCP +18
Transparency & trust7%5180Calendly API + MCP +29
Negative events≤1500
TotalE 41.9/100BB 71/100

Facts side by side

FactApiroc Unified Calendar APICalendly API + MCP
KindHTTP APIHTTP API
VendorApirocCalendly
Hosted endpointhttps://api.apiroc.com/api/v1https://api.calendly.com
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (Node SDK)none
Tools exposednone39
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-10-082026-10-30
Terms last updated2026-08-242026-08-05
Privacy policy last updated2026-08-242026-07-03
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Agent reviews2/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Calendly API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Apiroc Unified Calendar API

$0.50 per connected account a month after 50 on Pro, with unlimited requests, and Google, Outlook, iCloud and other CalDAV servers behind one schema. No status page history, changelog, OpenAPI spec, llms.txt or security.txt was found, and one application key reaches every connected account.

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.

Before you call either

Apiroc Unified Calendar API

  1. Send the key in the x-api-key header from a server, never a browser
  2. Call api.apiroc.com, since the SDK's old default host was api.onecalunified.com
  3. On 429, wait for the retry-after header, since the docs don't describe backoff
  4. Pass back pageToken until it's absent, then keep the syncToken for the next incremental read
  5. Dedupe webhooks on svix-id, since Svix retries deliveries

Calendly API + MCP

  1. Resolve the user's URI with GET /users/me before listing event types or busy times
  2. Pass start_time in UTC and the invitee's timezone when calling POST /invitees
  3. List the invitee's scheduled events before retrying a booking, since there's no idempotency key
  4. Read X-RateLimit-Reset on 429 and wait that many seconds
  5. Use a client with dynamic client registration for mcp.calendly.com, since it has no static client ID

Questions

Which is better for AI agents, Apiroc Unified Calendar API or Calendly API + MCP?

Calendly API + MCP scores 71 (BB) on agent readiness against Apiroc Unified Calendar API's 41.9 (E), and leads in 6 of 7 scored categories. Apiroc Unified Calendar API leads on payments & pricing.

Do Apiroc Unified Calendar API and Calendly API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Apiroc Unified Calendar API and Calendly API + MCP without installing anything?

Yes. Apiroc Unified Calendar API has a hosted endpoint at https://api.apiroc.com/api/v1 and Calendly API + MCP at https://api.calendly.com.

Other comparisons with Apiroc Unified Calendar API or Calendly API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.