Agent readiness · Scheduling and calendar APIs
cronofy.com
6 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. 1 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 and llms-full.txt present at https://www.cronofy.com/llms.txt and https://www.cronofy.com/llms-full.txt and https://docs.cronofy.com/llms.txt, but 1 of the 12 links we sampled across both files are gone, starting with https://www.cronofy.com/real-time-scheduling
- PASSDocs readable without JavaScript10,737 characters of text without JS, on https://docs.cronofy.com/developers/api/authorization/request-token/ rather than on https://docs.cronofy.com
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- 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
- FAILOAuth dynamic client registrationOAuth metadata published, but no registration_endpoint in it
- FAILMCP surfaceMCP mentioned 8x in your own files, but nothing answered at mcp.cronofy.com, mcp.cronofy.com/mcp, mcp.cronofy.com/v1/mcp, api.cronofy.com/mcp, /mcp or /api/mcp
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://app.cronofy.com/sign_up 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://app.cronofy.com/sign_up is reachable, but its form needs JavaScript
D · Provisioning
- PARTProgrammatic key provisioning1 of 7 provisioning phrases across the 7 documents we read: "service account"
- FAILFree tier or no-card trial stated in textNo free tier or no-card wording at https://www.cronofy.com/pricing
E · Integration
- FAILTyped SDK on the registrycronofy ships without bundled types, matched from the registry by who publishes it rather than by a link on your site
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://docs.cronofy.com
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 cronofy.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.