Is booqable.com agent ready?
booqable.com is largely agent ready: it scores 67/100 (grade B) on the w2agent rubric. Weakest areas: Agent Auth (38), Agent Discovery (48).
Changed since last check
No change in score since the previous check (2026-09-15)
Regressed: Response time, llms.txt links resolve
Changed: Token efficiency (HTML-to-text ratio) (partial → fail), Freshness signals (fail → partial)
Category scores
Technical
92
Agent Auth
38
Agent Discovery
48
Agent Protocols
54
Content Quality
76
Structured Data
88
Bot Accessibility
84
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ~Response timepartial
- ✓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 typepass
- ✓JSON-LD validpass
- ~Heading hierarchypartial
- ✓Schema.org JSON-LD presentpass
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✗Token efficiency (HTML-to-text ratio)fail
- ~Freshness signalspartial
- ✓Author attributionpass
- ✓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 schemasfail
- ✗/.well-known/ucpfail
- ✓Structured formspass
- —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 surfacepass
- —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)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ~Security headerspartial
Other
- —ecommerce-gtin-validskip
- —ecommerce-product-schemaskip
- —ecommerce-checkout-accessibleskip
Score history
- 67/100 · rubric v3.0
- 67/100 · rubric v3.0
- 67/100 · rubric v3.0
- 54/100 · rubric v2.0
- 54/100 · rubric v2.0
- 54/100 · rubric v2.0
- 54/100 · rubric v2.0