Agent readiness · Scheduling and calendar APIs
calendly.com
9 of 15 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 2 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- FAILllms.txt publishedllms.txt present at https://calendly.com/llms.txt, but 3 of the 12 links we sampled across the file are gone, starting with https://calendly.com/blog/calendly-vs-microsoft-bookings
- PASSDocs readable without JavaScript2,869 characters of text without JS, on https://developer.calendly.com/getting-started rather than on https://developer.calendly.com/
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- PASSPaths robots.txt points at answerthe 2 concrete paths your robots.txt allows all answer
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- PASSOAuth dynamic client registrationregistration_endpoint published
- PASSMCP surfaceLive MCP endpoint at https://mcp.calendly.com, answered 401 with an auth challenge
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://calendly.com/signup is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- FAILSignup reachable without a browserhttps://calendly.com/signup is reachable, but its form needs JavaScript
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 3 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://calendly.com/pricing: "Get started for free", "started for free", "Try for free"
E · Integration
- UNMEASUREDTyped SDK on the registryUnmeasurable: we could not identify the package a developer installs to use you, from your site, your docs or a registry searchName your package once in your docs, or link it from your repository, and we stop guessing. If your product is not something a developer installs, this check does not apply to you: unmeasured is out of the score and out of the denominator, so it costs you nothing.
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://developer.calendly.com/getting-started.md
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for calendly.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.