Browserbase
What it is
Connect your Browserbase account for web search, page fetch, and Stagehand browser interaction. The connection contains only an API key. Honeybase fixes the vendor endpoint; there is no base URL field.
Setup fields
These are the fields the guided setup collects — both the Add integration form and the setup card Barry raises in chat. Additional settings live on the connection's settings page once it exists.
Connection settings
| Field | Type | Required | Secret | Notes |
|---|---|---|---|---|
name | Text | Yes | No | A name that identifies this connection in the agent tool settings. |
Credentials
| Field | Type | Required | Secret | Notes |
|---|---|---|---|---|
apiKey | Password | Yes | Yes | Create an API key in your Browserbase dashboard (https://www.browserbase.com/settings), then paste it here. Honeybase stores the key in its secrets vault and masks it when you edit this connection. |
Connect your account
- Open the Browserbase dashboard and create an API key.
- In Honeybase, add a Browserbase integration, give it a name, and paste the key.
- Choose Test Connection, then save. Testing makes one small billable vendor request.
- In the agent builder, choose Browserbase as the web tool provider and this connection under Integration. Choosing Honeybase uses the server key instead.
A disabled, deleted, invalid, or exhausted connection produces an explicit tool error. Honeybase never falls back to its own key or another provider.
Web tools currently have no Honeybase credit debit. Your vendor may charge your account. Browser interaction costs still count toward the agent's run budget.
Browserbase Fetch does not run JavaScript. Use browser interaction for pages that require JavaScript. Stagehand defaults to the agent AI connection through Honeybase; its optional model override uses that same connection. Gateway mode uses Browserbase inference and is billed to the selected Browserbase account.
Connect the vendor's MCP server too
After saving this integration, select Connect vendor MCP too. Honeybase copies its saved API key server-side into a separate MCP connection and opens that connection's setup page. An equivalent connection is reused if one already exists. Sync the tool catalog, then review and approve the tools you want to expose. No tools are approved automatically.
The two connections are independent: changing or deleting the web provider key does not update or delete its MCP copy. Update both when rotating a key. This shortcut requires permission to manage integrations and an enabled, saved vendor connection. It never uses Honeybase's server key.
Administrators using the GraphQL API can call
integrations { connectVendorMcp(integrationId: ...) { publicId name } } as a
mutation, then use the existing MCP review and approval operations.