Is brivo.com agent ready?
brivo.com is partly agent ready: it scores 45/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (22), Agent Protocols (33), Content Quality (33), Structured Data (43), Agent Discovery (47).
Changed since last check
−6 points since the previous check (2026-09-16)
Regressed: FAQ content, JSON-LD valid, Reachable as Google-Agent, Reachable as ChatGPT-User, Reachable as Perplexity-User
Changed: Response time (partial → fail), Appropriate Schema.org type (partial → fail)
Category scores
Technical
72
Agent Auth
22
Agent Discovery
47
Agent Protocols
33
Content Quality
33
Structured Data
43
Bot Accessibility
83
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- 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 scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ✗Appropriate Schema.org typefail
- ✗JSON-LD validfail
- ✗Heading hierarchyfail
- ~Schema.org JSON-LD presentpartial
- ✗Schema.org completenessfail
Content Quality
- ✗FAQ contentfail
- ~Answer-first contentpartial
- ~Content lengthpartial
- ~Token efficiency (HTML-to-text ratio)partial
- ✗Freshness signalsfail
- ✗Author attributionfail
- ~Citation readinesspartial
- ~Lists and tables for structured infopartial
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 resolvepass
Agent Protocols
- ✓Discoverable API endpointspass
- ✗MCP endpointfail
- ✗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 supportfail
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ✗Agent/bot auth documentationfail
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ~Canonical URLspartial
- ✗Mobile viewportfail
- ~Content accessible without JSpartial
- ✓Security headerspass
Other
- ✓wp-page-builder-souppass
- ✓wp-rest-api-accessiblepass
- ✓wp-security-blocking-botspass
- ✓wp-robots-default-blockingpass
- ✓local-business-hours-jsonldpass
- ✓local-business-nap-structuredpass
- —local-business-booking-accessibleskip
Score history
- 45/100 · rubric v3.0
- 51/100 · rubric v3.0
- 51/100 · rubric v3.0
- 50/100 · rubric v2.0
- 49/100 · rubric v2.0
- 50/100 · rubric v2.0
- 50/100 · rubric v2.0