Is ai.backdocket.com agent ready?
ai.backdocket.com is not yet agent ready: it scores 34/100 (grade D) on the w2agent rubric. Weakest areas: Agent Discovery (0), Structured Data (0), Agent Protocols (23), Content Quality (26).
Changed since last check
+6 points since the previous check (2026-09-16)
Fixed: MCP endpoint, Response time, Token efficiency (HTML-to-text ratio)
Changed: Security headers (fail → partial)
Category scores
Technical
54
Agent Auth
69
Agent Discovery
0
Agent Protocols
23
Content Quality
26
Structured Data
0
Bot Accessibility
50
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryPresent
- MCP discoveryPresent
- llms.txt validityNot measured
Check results
Bot Accessibility
- ~No error status codespartial
- ✓Response timepass
- ✗XML sitemap existsfail
- ✓AI agent accesspass
- ?Edge treatment of agent user-agentstracked, not scorederror
- ✗robots.txt existsfail
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ✗OpenGraph meta tagsfail
- ✗Semantic HTML elementsfail
- ✗Appropriate Schema.org typefail
- —JSON-LD validskip
- ✗Heading hierarchyfail
- ✗Schema.org JSON-LD presentfail
- ✗Schema.org completenessfail
Content Quality
- ✗FAQ contentfail
- ✗Answer-first contentfail
- ~Content lengthpartial
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ~Citation readinesspartial
- ✓Lists and tables for structured infopass
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✗Discoverable API endpointsfail
- ✓MCP endpointpass
- ✗Action schemasfail
- —/.well-known/ucpskip
- —Structured formsskip
- —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 supportpass
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- ✓OAuth discovery chain (RFC 9728 → RFC 8414)pass
- —Developer portalskip
- —Scoped API permissionsskip
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✗UTF-8 charsetfail
- ✗Canonical URLsfail
- ✗Mobile viewportfail
- ~Content accessible without JSpartial
- ~Security headerspartial
Score history
- 34/100 · rubric v3.0
- 28/100 · rubric v3.0
- 28/100 · rubric v3.0
- 20/100 · rubric v2.0
- 20/100 · rubric v2.0
- 20/100 · rubric v2.0
- 20/100 · rubric v2.0
- 20/100 · rubric v2.0
- 20/100 · rubric v2.0
- 22/100 · rubric v2.0
- 22/100 · rubric v2.0