Is api.reve.com agent ready?
api.reve.com is not yet agent ready: it scores 28/100 (grade F) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Discovery (0), Content Quality (3), Agent Protocols (30).
Changed since last check
−4 points since the previous check (2026-09-16)
Fixed: Response time
Regressed: Answer-first content, Content accessible without JS, Citation readiness
Changed: Semantic HTML elements (partial → fail)
Category scores
Technical
58
Agent Auth
0
Agent Discovery
0
Agent Protocols
30
Content Quality
3
Structured Data
64
Bot Accessibility
53
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- 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 scoredpass
- ✗robots.txt existsfail
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ✗Semantic HTML elementsfail
- ✗Appropriate Schema.org typefail
- ✓JSON-LD validpass
- ✓Heading hierarchypass
- ✓Schema.org JSON-LD presentpass
- ~Schema.org completenesspartial
Content Quality
- ✗FAQ contentfail
- ✗Answer-first contentfail
- ✗Content lengthfail
- ✗Token efficiency (HTML-to-text ratio)fail
- ✗Freshness signalsfail
- ✗Author attributionfail
- ~Citation readinesspartial
- ✗Lists and tables for structured infofail
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 endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- —Structured formsskip
- —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 supportskip
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- —Developer portalskip
- —Scoped API permissionsskip
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✗Canonical URLsfail
- ✓Mobile viewportpass
- ✗Content accessible without JSfail
- ~Security headerspartial
Score history
- 28/100 · rubric v3.0
- 32/100 · rubric v3.0
- 32/100 · rubric v3.0
- 26/100 · rubric v2.0
- 26/100 · rubric v2.0
- 26/100 · rubric v2.0
- 26/100 · rubric v2.0
- 26/100 · rubric v2.0