Skip to main content
Integrations · Browserbase
Guild agents fetch web pages, search the web, and manage Browserbase cloud browser sessions, contexts, and functions. Guild stores your Browserbase API key and injects it server-side, so agent code never sees it. Credential policies decide which Browserbase operations each agent may call.

Book a demo

See how teams govern agents that use Browserbase.

Talk to sales

Get access to Guild, then connect Browserbase to your first agent.

What the Browserbase integration exposes

The integration is guildai~browserbase. Two tools return content directly: browserbase_fetch_create fetches a page with its headers and metadata, and browserbase_search_web returns structured search results. The rest manage Browserbase resources: sessions and their logs, recordings, and replays, contexts, downloads, extensions, certificates, functions and their invocations, and projects and usage. Requests go to https://api.browserbase.com.

How it works

1

Copy your Browserbase API key

Sign in to Browserbase and copy the API key from the dashboard.
2

Connect the key in Guild

Go to Access & setup > Credentials, click Connect, select browserbase, and paste the key into API Key.
3

Import the tools you need

Import BrowserbaseTools from @guildai-services/guildai~browserbase and use pick() to give the agent only the tools its job needs.

Authentication

  • Type: API key
  • Header: Guild sends the key as x-bb-api-key: <key>
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Tools are named with the browserbase_ prefix.

Tools

Tools in the latest published version of guildai~browserbase:

Frequently asked questions

No. browserbase_sessions_create starts a session and returns its connection details, but driving the page takes a Chrome DevTools Protocol client such as Playwright, which these tools don’t include. Use browserbase_fetch_create to read a page, or deploy a Browserbase function and call it with browserbase_functions_invoke.
Yes. A session runs until it times out or you release it, and Browserbase bills for that time. Have the agent end sessions with browserbase_sessions_update, and set a timeout when it creates them.
Yes. Write a credential policy that denies the delete operations. See Credential policies.
Also runs on Guild: Firecrawl · Pinecone Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 4, 2026