Browserbase

Subjects

• A
  robots.txt rules for AI agentsGood work.All 11 AI agents checked may fetch every key page. No AI agent is named, so they all fall back to the * group.Extra credit: Add explicit User-agent groups for the AI agents you want, so your policy is a decision rather than a default.
• B
  llms.txt and llms-full.txtGood work./llms.txt found (16878 chars, 113 link(s)). No /llms-full.txt.Extra credit: Improve llms.txt: publish /llms-full.txt with the full docs inlined.
• A
  SitemapGood work.Sitemap at https://browserbase.com/sitemap.xml (from robots.txt) with 386 entries.
• A
  Server-rendered readable HTMLGood work.All 1 key page(s) return readable HTML without running JavaScript.
• B
  Markdown versions of key pagesGood work.Every key page has a markdown version.Extra credit: Advertise the markdown versions of / with <link rel="alternate" type="text/markdown">.
• A
  Structured data (JSON-LD)Good work.Every key page has valid JSON-LD.
• B
  OpenAPI and API docs discoverabilityGood work.Key pages link to an API spec (https://docs.browserbase.com/reference/api/openapi.v1.yaml).Extra credit: Also serve the spec at /openapi.json and list it in llms.txt so agents find it without crawling.
• C
  MCP server discoverabilityMentions MCP, never shows up with it.An MCP endpoint is documented (https://docs.browserbase.com/integrations/mcp), but no /.well-known MCP discovery document.Extra credit: Publish /.well-known/mcp.json describing the server. Discovery through /.well-known/mcp.json is still a draft proposal, so also document the server URL, transport, and auth in llms.txt and your docs.
• A
  Auth, signup, and bot-challenge frictionGood work.No login walls, bot challenges, or CAPTCHAs on 1 key page(s).
• A
  Page weight and token costGood work.Key pages are light enough to read in one pass.