Agent readiness · Scheduling and calendar APIs
timekit.io
7 of 14 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)
- PASSllms.txt publishedllms.txt present at https://developers.timekit.io/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript6,399 characters of text without JS, on https://developers.timekit.io/reference/authentication rather than on https://developers.timekit.io/reference/getting-started
- 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 registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomains
- FAILMCP surfaceNo MCP surface: nothing answered at mcp.timekit.io, mcp.timekit.io/mcp, mcp.timekit.io/v1/mcp, api.timekit.io/mcp, /mcp or /api/mcp, and no file mentions MCP
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://www.timekit.io/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
- UNMEASUREDSignup reachable without a browserUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://www.timekit.io/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 5 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://www.timekit.io/pricing: "free plan", "free trial", "free forever"
E · Integration
- FAILTyped SDK on the registrytimekit-booking 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://developers.timekit.io/reference/getting-started
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 timekit.io 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.