Is databuddy.cc agent ready?
databuddy.cc is largely agent ready: it scores 63/100 (grade B) on the w2agent rubric. Weakest areas: Agent Auth (38), Agent Protocols (42).
Changed since last check
No change in score since the previous check (2026-09-15)
Fixed: Markdown alternate links
Regressed: Response time
Category scores
Technical
91
Agent Auth
38
Agent Discovery
84
Agent Protocols
42
Content Quality
65
Structured Data
58
Bot Accessibility
79
Agent protocol panel
- A2A agent cardPresent
- OAuth discoveryNot found
- 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 scoredpass
Structured Data
- ✓OpenGraph meta tagspass
- ✓Semantic HTML elementspass
- ✗Appropriate Schema.org typefail
- ✗JSON-LD validfail
- ✓Heading hierarchypass
- ~Schema.org JSON-LD presentpartial
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✗Answer-first contentfail
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✓Author attributionpass
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- ✓MCP server cardtracked, not scoredpass
- ✓Markdown alternate linkspass
- ~/.well-known/agent-card.jsonpartial
- ✓llms.txt links resolvepass
Agent Protocols
- ✓Discoverable API endpointspass
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✗Structured formsfail
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✗PKCE S256 supportfail
- ~Public API surfacepartial
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- ~Agent/bot auth documentationpartial
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ✓Developer portalpass
- ~Scoped API permissionspartial
- ✓API catalog (RFC 9727)pass
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- ✓nextjs-metadata-apipass
- ~nextjs-static-generationpartial
- ✓nextjs-well-known-servedpass
- —local-business-hours-jsonldskip
- —local-business-nap-structuredskip
- —local-business-booking-accessibleskip
Score history
- 63/100 · rubric v3.0
- 63/100 · rubric v3.0
- 63/100 · rubric v3.0
- 47/100 · rubric v2.0
- 47/100 · rubric v2.0
- 47/100 · rubric v2.0
- 47/100 · rubric v2.0
- 46/100 · rubric v2.0