Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: API key.
  • Connection: The key from BROWSERBASE_API_KEY is sent as the X-BB-API-Key header.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Create a Browserbase account: Sign up at https://www.browserbase.com - the free plan includes browser hours for testing.
  2. Copy your API key and project ID: In the dashboard, open Settings to find your API key (bb_…) and your default project ID. Each key belongs to a project.
  3. Store the key: Add it to your .env file as BROWSERBASE_API_KEY=bb_… - requests authenticate with the X-BB-API-Key header.
  4. Verify access: Run the List Projects tool, then List Sessions. Create Session can omit projectId - it is inferred from the API key.

​
Provider notes

  • Sessions are billed by browser minutes - release sessions you are done with via the Release Session tool
  • Driving the browser (navigation, clicks) happens over the session’s CDP connectUrl with Playwright/Puppeteer/Stagehand, not through this REST API
  • keepAlive sessions are only available on paid plans
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as browserbase__list_sessions with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.