◎ Discry Score
clockwise.com
productivity · API
F
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 92 (A)
Discry your API →
PRODUCTIVITY · RANK #24 OF 24

Clockwise is Not Agent-Ready to agents.

Discry independently scored how well an AI agent can discover and understand the Clockwise API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 0/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Fail
llms.txtAn llms.txt index that points agents to the docs that matter.Fail
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Fail
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Fail
SitemapA sitemap so agents can enumerate the docs surface.Fail

Comprehension

55% of score · 0/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Fail
Realistic examplesRunnable, real-world request/response examples.Fail
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Fail
Error-recovery guidanceDocumented failure modes and how to recover from them.Fail
Answer-first formatThe answer leads; preamble does not bury it.Fail
Capability boundariesClear limits — what the API can and cannot do.Fail
Naming consistencyConsistent, predictable naming across endpoints.Fail
Heading hierarchyClean heading structure agents can navigate.Fail
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Fail
Token efficiencyDocs are concise enough to fit an agent context window.Fail

What we found

  • An agent trying to reach the Clockwise developer surface today hits a dead end: every path on getclockwise.com (including /mcp, /overview, /blog/*, robots.txt, llms.txt, sitemap.xml, and .well-known/mcp.json) returns HTTP 200 but serves only a static 'joining Salesforce' shutdown notice, so effective 404s are masked as successful responses.
  • The product is being discontinued (support ends March 27, 2026; the assessment date of June 30, 2026 is past that), and both the developer.getclockwise.com and support.getclockwise.com subdomains fail DNS resolution entirely, so no reference docs, quickstart, or knowledge base is retrievable.
  • Clockwise had genuinely notable agent-readiness credentials before shutdown — it publicly launched what it billed as the 'first MCP Server for Time' in September 2025 for Claude, Cursor, and ChatGPT — but that surface is now gone, so an agent has zero live signal to act on.
  • Search results for 'Clockwise API' surface unrelated third-party products (an IoT device API at clockwise.page and clockwisehq GitHub org, an SMS API at clockwisesms), which would actively mislead an agent trying to disambiguate the getclockwise.com AI calendar tool.
  • No OpenAPI spec, AGENTS.md, or MCP registry entry is reachable for the getclockwise.com product; discovery and comprehension both score zero because no assessable documentation exists at any resolvable URL.

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Not actionable for the vendor — Clockwise is shutting down and joining Salesforce. This entry should be flagged in the Discry Directory as DISCONTINUED / sunset rather than scored as a live agent-readiness target.
  2. 02If the directory retains this record, annotate it clearly: product offline as of March 27, 2026; former MCP server and API docs no longer resolve; direct agents/users to the recommended successor (Reclaim.ai) or to Salesforce's agentic calendar offerings.
  3. 03For directory hygiene, add a disambiguation note distinguishing the getclockwise.com AI calendar tool from the unrelated 'Clockwise' IoT device API (clockwise.page / clockwisehq) and Clockwise SMS (clockwisesms), which pollute API-discovery searches.
  4. 04Deprioritize any future re-scan of getclockwise.com; re-evaluate only if Clockwise scheduling capabilities re-emerge under a Salesforce-hosted domain with a resolvable developer surface.

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

✕ Error format documented✕ Rate limits documented✕ Pagination documented✕ Idempotency documented

No execution characteristics are documented at an accessible URL. Clockwise is winding down (team joining Salesforce; product offline as of March 27, 2026), and the entire getclockwise.com domain now serves only a single shutdown-notice page. The developer and support subdomains no longer resolve, and the previously-launched Clockwise MCP server (getclockwise.com/mcp, 'first MCP Server for Time', Sept 2025) is no longer reachable. Nothing about auth, errors, rate limits, pagination, or idempotency can be assessed.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free