Is cutt.ly agent ready?
cutt.ly is partly agent ready: it scores 58/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (22), Agent Discovery (42), Agent Protocols (46).
Changed since last check
+2 points since the previous check (2026-09-16)
Fixed: Heading hierarchy, Reachable as Google-Agent, Reachable as Perplexity-User
Regressed: Response time, JSON-LD valid
Changed: Freshness signals (fail → partial), Author attribution (fail → partial), llms.txt links resolve (fail → partial)
Category scores
Technical
98
Agent Auth
22
Agent Discovery
42
Agent Protocols
46
Content Quality
75
Structured Data
65
Bot Accessibility
79
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ?Edge treatment of agent user-agentstracked, not scorederror
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ✓OpenGraph meta tagspass
- ✓Semantic HTML elementspass
- ~Appropriate Schema.org typepartial
- ~JSON-LD validpartial
- ✓Heading hierarchypass
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ~Freshness signalspartial
- ~Author attributionpartial
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ~llms.txt links resolvepartial
Agent Protocols
- ✓Discoverable API endpointspass
- ✗MCP endpointfail
- ✓Action schemaspass
- ✗/.well-known/ucpfail
- ~Structured formspartial
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✗Reachable as ChatGPT-Userfail
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✗PKCE S256 supportfail
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ✗Agent/bot auth documentationfail
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- —ecommerce-gtin-validskip
- ✓ecommerce-product-schemapass
- —ecommerce-checkout-accessibleskip
Score history
- 58/100 · rubric v3.0
- 56/100 · rubric v3.0
- 57/100 · rubric v3.0
- 33/100 · rubric v2.0
- 33/100 · rubric v2.0
- 38/100 · rubric v2.0
- 37/100 · rubric v2.0