Browserbase integration

Developer Tools & Infrastructure · 3 actions · API key auth

Cloud browser infrastructure for running and managing headless browser sessions

Put Browserbase to work View Browserbase integration docs

Overview

The ModuleX Browserbase integration lets a ModuleX agent operate Browserbase on your behalf — running create and list actions across contexts, sessions and projects — directly from a plain-English request, using your organization's own Browserbase credentials. No pre-built workflow is required: the agent picks the right Browserbase action for the task.

Browserbase is a developer tools & infrastructure platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Browserbase action — or, when you want a repeatable process, the composer assembles a Browserbase workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Browserbase in plain English

Type what you want. A ModuleX agent picks the right Browserbase action — or chains several — and runs it. No workflow to build.

Creates a new context in Browserbase for persistent browser state
resolves tocreate_context
Show me the projects that match what I describe
resolves tolist_projects

Use cases

What you can automate with Browserbase

Create a context straight from a requestcreate_context
Pull a list of projects for a reportlist_projects
Creates a new browser session with specified settingscreate_session

At a glance

Browserbase integration at a glance

VendorBrowserbase

CategoryDeveloper Tools & Infrastructure

Actions available3

AuthenticationAPI key

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 3 Browserbase actions

Contexts1

create_context

Creates a new context in Browserbase for persistent browser state

Sessions1

create_session

Creates a new browser session with specified settings

Projects1

list_projects

Lists all projects in the Browserbase account

See full parameters and response schemas in the Browserbase integration docs

Two ways

Two ways to use Browserbase in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Browserbase action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Browserbase into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Browserbase

API keyBrowserbase uses API-key authentication. You provide your own Browserbase secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use Browserbase without re-authenticating.

Step-by-step setup in the Browserbase docs

Pairs well with Browserbase

Agents often chain Browserbase with these — connect them once and the agent can use all of them in a single task.

FAQ

Browserbase + ModuleX FAQ

A ModuleX agent can run any of Browserbase's 3 actions — across contexts, sessions and projects — from a plain-English request, using your organization's own Browserbase credentials.

No. The agent selects the right Browserbase action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Via your own Browserbase API key, stored encrypted and scoped to your organization.

3, spanning contexts, sessions and projects.

Browserbase runs on your own credentials, so any Browserbase usage is billed by Browserbase directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Browserbase to work in ModuleX.

Connect Browserbase once with your own credentials and let your agent run all 3 actions on demand.

Put Browserbase to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →