Is browser-use.com agent ready?

browser-use.com is partly agent ready: it scores 59/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (12).

59/ 100
Grade: C

Last checked · Platform: nextjs

Scored Oct 14, 2026 · Rubric v3.0

Changed since last check

−14 points since the previous check (2026-09-16)

Regressed: Public API surface, OAuth discovery chain (RFC 9728 → RFC 8414), Content negotiation (Markdown), Lists and tables for structured info

Category scores

Technical
89
Agent Auth
12
Agent Discovery
50
Agent Protocols
73
Content Quality
53
Structured Data
70
Bot Accessibility
93

Agent protocol panel

  • A2A agent cardNot found
  • OAuth discoveryNot found
  • MCP discoveryPresent
  • llms.txt validityPresent

Check results

Bot Accessibility

  • ✓No error status codespass
  • ✓Response timepass
  • ✓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 scoredpass

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 signalspartial
  • ✗Author attributionfail
  • ✓Citation readinesspass
  • ~Lists and tables for structured infopartial

Agent Discovery

  • ✓llms.txt follows specpass
  • ✓llms.txt existspass
  • —MCP server cardtracked, not scoredskip
  • ✓Markdown alternate linkspass
  • ✗/.well-known/agent-card.jsonfail
  • ✓llms.txt links resolvepass

Agent Protocols

  • ✓Discoverable API endpointspass
  • ✓MCP endpointpass
  • ✗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)partial
  • —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)fail
  • —Developer portalskip
  • —Scoped API permissionsskip
  • —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
  • 73/100 · rubric v3.0
  • 73/100 · rubric v3.0
  • 55/100 · rubric v2.0
  • 55/100 · rubric v2.0
  • 54/100 · rubric v2.0
  • 53/100 · rubric v2.0
  • 45/100 · rubric v2.0
  • 45/100 · rubric v2.0
  • 45/100 · rubric v2.0
  • 46/100 · rubric v2.0

Related websites