Is ably.net agent ready?
ably.net is not yet agent ready: it scores 42/100 (grade D) on the w2agent rubric. Weakest areas: Agent Protocols (8), Agent Discovery (13), Agent Auth (27), Structured Data (27).
Changed since last check
−3 points since the previous check (2026-09-16)
Fixed: OpenGraph meta tags, Response time, Developer portal
Regressed: llms.txt exists, Reachable as ChatGPT-User
Files removed: llms.txt
Category scores
Technical
96
Agent Auth
27
Agent Discovery
13
Agent Protocols
8
Content Quality
66
Structured Data
27
Bot Accessibility
67
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✓Response timepass
- ✗XML sitemap existsfail
- ✓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 typefail
- ✗JSON-LD validfail
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✓Markdown alternate linkspass
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- ~Structured formspartial
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✗Reachable as Google-Agentfail
- ✗Reachable as ChatGPT-Userfail
- ✗Reachable as Perplexity-Userfail
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✗PKCE S256 supportfail
- ✓Public API surfacepass
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- ✗Agent/bot auth documentationfail
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Score history
- 42/100 · rubric v3.0
- 45/100 · rubric v3.0
- 50/100 · rubric v3.0
- 38/100 · rubric v2.0
- 38/100 · rubric v2.0
- 45/100 · rubric v2.0
- 43/100 · rubric v2.0