# Calendly — API Agent Score

> Score: 63/100 (Grade: C) | Domain: calendly.com | Rubric: 1.0.0 | Checked: July 24, 2026

Calendly scored 63/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/calendly)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 63/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 87/100 (A)
- Developer Experience: 55/100 (D)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 72/100 (B)
- Agent Usability: 43/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — authentication documented in the docs site at https://developer.calendly.com/authentication. Investigated: docs 100%, wellknown 100%, spec 50%.
- [warn] Machine-readable, versioned contract — info.version="2.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [warn] Schema coverage & depth — 90% of operations have documented schemas (target 95%+). Investigated: spec 67%, sdk 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.

### Developer Experience

- [pass] Description completeness — 97% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 0%.
- [pass] Changelog published — changelog documented in the docs site at https://developer.calendly.com/release-notes. Investigated: spec 100%, docs 100%.
- [warn] Quickstart present — Quickstart page reachable (10 variants scanned starting at https://developer.calendly.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Self-service developer portal — Signup page is sales-gated (contact-sales/request-access language detected). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/developer_calendly, 1007 snippets). Investigated: docs 100%, sdk 92%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — 34 of 34 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.calendly.com/llms.txt, https://developer.calendly.com/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (34 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 7 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 93% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 1 of 34 pages appear to be client-side rendered SPA shells (___gatsby detected); agents using HTTP fetches will see no content; 1 more have page structure but little substantive content. Investigated: docs 57%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 2% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Calendly's API Design is a genuine strength — the contract is clean and machine-readable, giving partners a solid foundation to build against. However, two areas are holding the partner program back: Agent Usability is critically weak, meaning partners and their AI agents cannot reliably run real workflows (missing runnable examples, no idempotency guidance, and no rate-limit signaling), and Agent Understanding is inconsistent, with gaps in structured docs, agent instruction files, and parseable context that prevent AI agents from acting on the API without guessing. Prioritize making the API operationally trustworthy for agents first, then ensure every doc surface is machine-readable and self-serve onboarding is friction-free.