{
  "company": "Browserbase",
  "slug": "browserbase",
  "website": "https://www.browserbase.com",
  "audit_date": "2026-04-05",
  "overall_score": 47,
  "tier": "Human-Dependent",
  "tier_as_published": "H",
  "pillars": {
    "P1": {
      "name": "Signal Architecture",
      "score": 13,
      "max": 25
    },
    "P2": {
      "name": "Clarity Stack",
      "score": 13,
      "max": 25
    },
    "P3": {
      "name": "Trust Envelope",
      "score": 8,
      "max": 20
    },
    "P4": {
      "name": "Velocity Triggers",
      "score": 6,
      "max": 10
    },
    "P5": {
      "name": "Gravity Design",
      "score": 7,
      "max": 20
    }
  },
  "criteria": [
    {
      "id": "P1-A",
      "pillar": "P1",
      "name": "Structured Data",
      "score": 1,
      "max": 5,
      "evidence": "No evidence of schema.org markup, JSON-LD, or Organization/Product/Offer schema found on homepage or pricing pages. Sitemap exists but no structured data layer."
    },
    {
      "id": "P1-B",
      "pillar": "P1",
      "name": "Machine-Readable Pricing",
      "score": 3,
      "max": 5,
      "evidence": "Pricing table clearly presents four tiers (Free $0, Developer $20/mo, Startup $99/mo, Scale custom) in HTML with specific caps and overage rates. Not tagged with schema.org/Offer but numeric structure is machine-parseable."
    },
    {
      "id": "P1-C",
      "pillar": "P1",
      "name": "llms.txt / Agent Layer",
      "score": 2,
      "max": 5,
      "evidence": "A file exists at docs.browserbase.com/llms.txt but it functions only as a documentation link index without substantive content. No proper agent-facing identity or usage guidance. Not present at root domain."
    },
    {
      "id": "P1-D",
      "pillar": "P1",
      "name": "API / MCP Availability",
      "score": 4,
      "max": 5,
      "evidence": "Full REST API and SDKs for Node.js and Python. Published MCP server (`npx @browserbasehq/mcp-server-browserbase`) with 8 documented tools. Integrations with LangChain, crewAI, OpenAI, Claude, Gemini. No publicly linked OpenAPI/Swagger spec found, preventing a score of 5."
    },
    {
      "id": "P1-E",
      "pillar": "P1",
      "name": "Discoverability (GEO)",
      "score": 3,
      "max": 5,
      "evidence": "Strong presence in AI tool roundups, named in blog posts and framework docs. Used by Perplexity, Vercel, Microsoft, DeepMind. SEO-quality content exists across docs and blog. Not yet structured for AI retrieval optimization beyond standard SEO."
    },
    {
      "id": "P2-A",
      "pillar": "P2",
      "name": "Offer Completeness",
      "score": 3,
      "max": 5,
      "evidence": "What (headless browser infrastructure), who (AI agents/developers), and pricing (tiers visible) are findable but not co-located in a single machine-readable source. The pricing page and product page are separate; no single document captures the full offer."
    },
    {
      "id": "P2-B",
      "pillar": "P2",
      "name": "Scope & Limits",
      "score": 4,
      "max": 5,
      "evidence": "Pricing page explicitly states: browser hours per plan, concurrent browser caps (3/25/100/250+), session duration (15 min to 6+ hrs), proxy GB allotments, RPS limits per API, data retention windows (7\u201330+ days), and overage rates ($0.10\u2013$0.12/hr). Strong coverage."
    },
    {
      "id": "P2-C",
      "pillar": "P2",
      "name": "Substitution Rules",
      "score": 1,
      "max": 5,
      "evidence": "No guidance found on service unavailability, fallback behavior, or substitution options. Status page documents incidents only after they occur with no pre-stated contingency."
    },
    {
      "id": "P2-D",
      "pillar": "P2",
      "name": "Conditional Logic Transparency",
      "score": 2,
      "max": 5,
      "evidence": "Scale tier is opaque (\"contact sales,\" custom pricing). Enterprise conditions undisclosed. Free and paid tiers are well-defined but a significant portion of the offer surface is hidden behind sales."
    },
    {
      "id": "P2-E",
      "pillar": "P2",
      "name": "Semantic Precision",
      "score": 3,
      "max": 5,
      "evidence": "Mix of precise claims (2 vCPUs per instance, 15-minute session limit on Free, $0.12/hr overage) and vague marketing language (\"robust,\" \"reliable,\" \"powerful\"). Core technical specs are quantified; positioning copy is not."
    },
    {
      "id": "P3-A",
      "pillar": "P3",
      "name": "Verifiable Performance Data",
      "score": 2,
      "max": 5,
      "evidence": "Public status page (status.browserbase.com) exists with 5 monitored components and documented incident history since August 2024. However, no uptime percentage is published, no formal SLA is stated, and an independent benchmark (AIMultiple) reported a 50% task success rate in single-task evaluations, which undercuts self-reported reliability."
    },
    {
      "id": "P3-B",
      "pillar": "P3",
      "name": "Scoped Permissions",
      "score": 2,
      "max": 5,
      "evidence": "Authentication requires BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID, creating project-level scoping. No evidence of agent-specific time-bounded, amount-bounded, or action-bounded permission tiers. SOC-2 Type 1 and HIPAA compliance exist but permission granularity is limited."
    },
    {
      "id": "P3-C",
      "pillar": "P3",
      "name": "Audit Trail",
      "score": 2,
      "max": 5,
      "evidence": "Session recording, command logging, live view iFrame, and source capture are available \u2014 but these are developer debugging tools. No machine-accessible audit log API for agent systems was found, nor evidence of structured transaction logs consumable by an orchestrating agent."
    },
    {
      "id": "P3-D",
      "pillar": "P3",
      "name": "Behavioral Consistency",
      "score": 2,
      "max": 5,
      "evidence": "SOC-2 Type 1 certification exists. Status page tracks incidents. No version-controlled terms of service, no published notice periods for API changes, and no documented stability track record for the API surface itself beyond the incident log."
    },
    {
      "id": "P4-A",
      "pillar": "P4",
      "name": "Friction-Free Activation",
      "score": 4,
      "max": 5,
      "evidence": "Free tier requires no credit card. MCP server installed via a single `npx` command. API key issued self-serve. Developer tier activatable at $20/mo without human approval. Activation path is close to instant with no sales gate for the first three tiers."
    },
    {
      "id": "P4-B",
      "pillar": "P4",
      "name": "Agent Decision Signals",
      "score": 2,
      "max": 5,
      "evidence": "Free tier serves as a trial signal (1 browser hour, 3 concurrent). No programmatic signals explicitly designed for agent consumption (e.g., no capability-check endpoint, no machine-readable upgrade triggers, no structured \"when to scale\" guidance)."
    },
    {
      "id": "P5-A",
      "pillar": "P5",
      "name": "Integration Depth",
      "score": 3,
      "max": 5,
      "evidence": "Supports Playwright, Puppeteer, Selenium, LangChain, crewAI; open-source Stagehand framework creates additional ecosystem lock-in. Teams that adopt Stagehand or build production pipelines around Browserbase sessions accumulate meaningful switching cost."
    },
    {
      "id": "P5-B",
      "pillar": "P5",
      "name": "Agent Memory Layer",
      "score": 2,
      "max": 5,
      "evidence": "Session persistence is supported (\"sessions that persist across runs so agents stay logged in\") and sessions can run up to 6+ hours on Scale. But there is no rich, structured agent-accessible memory layer \u2014 no cross-session context store, preference API, or agent-identity persistence beyond browser cookies."
    },
    {
      "id": "P5-C",
      "pillar": "P5",
      "name": "Programmatic Renewal",
      "score": 1,
      "max": 5,
      "evidence": "Standard SaaS billing via subscription. No evidence of a renewal API, usage-triggered upgrade hooks, or any mechanism for an agent to programmatically manage its own subscription lifecycle."
    },
    {
      "id": "P5-D",
      "pillar": "P5",
      "name": "Compounding Value Signal",
      "score": 1,
      "max": 5,
      "evidence": "Session recordings and usage history accumulate, but no agent-readable signal surfaces compounding value (e.g., \"your agent has solved 1,200 CAPTCHAs with 97% success \u2014 here's your efficiency trend\"). Value accrues operationally but is not legible to agents."
    }
  ],
  "strongest_signals": [
    {
      "title": "MCP server is published and installable",
      "detail": "\u2014 `npx @browserbasehq/mcp-server-browserbase` with 8 documented tools. Agents can integrate in minutes. This is the strongest agent-native signal in the entire stack."
    },
    {
      "title": "Pricing limits are explicit and granular",
      "detail": "\u2014 browser hours, concurrent caps, session duration, proxy GB, RPS, and overage rates are all stated per plan. An agent evaluating cost-to-capability has real data to work with."
    },
    {
      "title": "Friction-free activation",
      "detail": "\u2014 No credit card required for free tier; no human approval gate on the first three tiers. An agent can self-provision access immediately."
    }
  ],
  "critical_gaps": [
    {
      "title": "No structured data / schema markup",
      "detail": "\u2014 The homepage and pricing page carry zero schema.org signals. AI crawlers and retrieval systems cannot parse the offer without human interpretation."
    },
    {
      "title": "No formal SLA or uptime commitment",
      "detail": "\u2014 19+ outages documented over 8 months; no published uptime %; no SLA contract visible. This is a trust blocker for agent systems that need reliable infrastructure guarantees."
    },
    {
      "title": "No machine-accessible audit trail",
      "detail": "\u2014 Debugging tools exist for humans (session recordings, live view) but no structured log API for agent orchestrators to verify what happened during a session."
    },
    {
      "title": "Scale tier opacity",
      "detail": "\u2014 A significant portion of the customer base (enterprise/high-volume) operates on \"contact sales\" terms. An agent evaluating fit for scale cannot determine cost or conditions without human mediation."
    }
  ],
  "priority_actions": [
    {
      "action": "Publish a public uptime SLA",
      "points_gain": 5,
      "pillar": "P3",
      "effort": "Low"
    },
    {
      "action": "Add schema.org/Offer markup to the pricing page",
      "points_gain": 4,
      "pillar": "P1",
      "effort": "Low"
    },
    {
      "action": "Upgrade llms.txt to substantive agent-facing content",
      "points_gain": 3,
      "pillar": "P1",
      "effort": "Low"
    },
    {
      "action": "Publish a machine-accessible session log API",
      "points_gain": 3,
      "pillar": "P3",
      "effort": "Medium"
    },
    {
      "action": "Add explicit agent-scoped permission tiers",
      "points_gain": 3,
      "pillar": "P3",
      "effort": "Medium"
    }
  ],
  "executive_summary": "Browserbase scores 47/100 (Human-Dependent), landing in the tier where AI agents can discover and integrate the product but cannot fully evaluate, trust, or autonomously manage it. Its strongest signal is the published MCP server and granular pricing limits \u2014 a developer (or an agent doing research) can get hands-on quickly. The critical failure points are structural: no schema markup means AI crawlers cannot parse the offer, no published SLA means agents cannot verify reliability commitments, and no audit log API means orchestrators cannot inspect what their agents did. The single highest-ROI action is publishing a formal uptime SLA \u2014 it costs almost nothing operationally but removes the biggest trust blocker for autonomous purchasing decisions.",
  "rubric_version": "v1-2026-04 (20 criteria, 100 raw points; P3-E Agent Registration added to rubric v2 in 2026-06, not scored in this audit)",
  "framework": "Agent Native Offers \u2014 The Agent Sale framework",
  "source_file": "2026-04-05 \u2014 Browserbase \u2014 Agent Native Offer Audit.md",
  "rank": 22
}