Is qase.io agent ready?
qase.io is partly agent ready: it scores 59/100 (grade C) on the w2agent rubric.
Changed since last check
−12 points since the previous check (2026-09-15)
Regressed: PKCE S256 support, Response time, Agent/bot auth documentation, OAuth discovery chain (RFC 9728 → RFC 8414), llms.txt links resolve
Changed: Scoped API permissions (partial → fail), Schema.org completeness (fail → partial)
Category scores
Category breakdown not recorded for this audit.
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryPresent
- 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 scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ✓OpenGraph meta tagspass
- ~Semantic HTML elementspartial
- ~Appropriate Schema.org typepartial
- ✓JSON-LD validpass
- ✓Heading hierarchypass
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✗Answer-first contentfail
- ✓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 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 endpointpass
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✓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)pass
- ✗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)fail
- ✓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 headerspartial
Other
- ✓nextjs-metadata-apipass
- ✓nextjs-static-generationpass
- ✗nextjs-well-known-servedfail
Score history
- 59/100 · rubric v3.0
- 71/100 · rubric v3.0
- 40/100 · rubric v2.0
- 40/100 · rubric v2.0
- 40/100 · rubric v2.0
- 40/100 · rubric v2.0
- 39/100 · rubric v2.0
- 40/100 · rubric v2.0
- 43/100 · rubric v2.0