Browserbase is a serverless platform that enables developers to run, manage, and monitor headless browsers at scale, offering seamless integration with tools like Playwright, Puppeteer, and Selenium.
Browserbase is a serverless platform that enables developers to run, manage, and monitor headless browsers at scale, offering seamless integration with tools like Playwright, Puppeteer, and Selenium. On Nagent, Browserbase is exposed as a fully-configurable developer tools integration that any agent can call — 19 actions, and API key authentication. No code is required to wire Browserbase into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Browserbase to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Browserbase into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Browserbase, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BROWSERBASE_TOOL_CONTEXTS_CREATETool to create a new browser context. Use when you need to obtain upload credentials for a custom user-data-directory in a project.
Input parameters
The Project ID. Can be found in Settings.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_CONTEXTS_GETTool to retrieve details of a specific browser context. Use when you have a context ID and need its metadata.
Input parameters
Unique identifier of the browser context to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_CONTEXTS_UPDATETool to update a specific browser context. Use when you need fresh upload URL and encryption details for an existing context, after obtaining a valid context ID.
Input parameters
The unique identifier of the browser context to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_CREATE_BROWSER_SESSIONTool to create a new browser session. Use when you need an isolated browser context before performing any page interactions.
Input parameters
Region for the session, e.g. 'us-west-2', 'us-east-1'.
Optional proxy configuration for the session.
Session timeout in seconds.
Whether to keep the session alive after disconnection.
Project ID to associate with the browser session.
The ID of the custom extension to load.
Custom metadata object for the session. All values must be strings. The entire metadata object is limited to 512 characters when serialized to JSON. Note: The API has been observed to reject certain string patterns including URLs and strings containing '://' - use simple alphanumeric strings with underscores/hyphens. Examples: {'purpose': 'navigation', 'env': 'staging', 'testId': 'test-123'}.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_DELETE_CONTEXTTool to delete a browser context and all its stored data (cookies, localStorage, etc.). Use when you need to permanently remove a context.
Input parameters
Unique identifier of the browser context to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_DELETE_EXTENSIONTool to delete an uploaded browser extension by its ID. Use when you need to remove an extension from Browserbase.
Input parameters
Unique identifier of the browser extension to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_DELETE_SESSION_DOWNLOADSTool to delete all file downloads from a specific browser session. Use when you need to clean up session artifacts or free storage space.
Input parameters
Unique identifier of the session to delete downloads from
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_GET_EXTENSIONTool to retrieve details of a specific browser extension. Use when you have an extension ID and need its metadata (file name, timestamps, project ID).
Input parameters
Unique identifier of the browser extension to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_GET_PROJECTTool to retrieve details of a specific project including settings and configuration. Use when you have a project ID and need its metadata.
Input parameters
Unique identifier of the project to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_GET_PROJECT_USAGETool to retrieve usage statistics for a project including browser minutes and proxy bytes consumed. Use when you need to monitor or track resource usage for a specific project.
Input parameters
Unique identifier of the project to retrieve usage statistics for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_LIST_PROJECTSTool to list all projects for the authenticated account. Use when you need to retrieve all projects associated with the current API key.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_SESSIONS_GETTool to retrieve details of a specific browser session. Use when you have a session ID and need its metadata (status, URLs, timestamps).
Input parameters
Unique identifier of the browser session to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_SESSIONS_GET_DEBUGTool to retrieve live debug URLs for a specific session. Use when you need to connect to a running session for debugging.
Input parameters
Unique identifier of the session to retrieve debug URLs for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_SESSIONS_GET_DOWNLOADSTool to download files from a specific session. Use after session completion to retrieve all generated artifacts in a ZIP archive.
Input parameters
Unique identifier of the session to download artifacts from
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_SESSIONS_GET_LOGSTool to retrieve logs of a specific session. Use after actions in a session to inspect network events and data exchange.
Input parameters
Unique identifier of the session to retrieve logs for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_SESSIONS_LISTTool to list all browser sessions. Use when you need to retrieve sessions with optional filtering by status or metadata query.
Input parameters
Query sessions by user metadata. Format: user_metadata\['key'\]:'value' or for nested keys: user_metadata\['key1'\]\['key2'\]:'value'.
Filter sessions by status. Available options: RUNNING, ERROR, TIMED_OUT, COMPLETED.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_SESSIONS_UPDATETool to update the status of a specific browser session. Use when you need to request session completion before timeout to avoid additional charges.
Input parameters
Unique identifier of the browser session to update
Set to REQUEST_RELEASE to request that the session complete before its timeout
The Project ID linked to the session
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_UPLOAD_EXTENSIONTool to upload a browser extension for use in sessions. Supports Chrome extension format (ZIP). Use when you need to add custom browser extensions to your Browserbase project.
Input parameters
The browser extension file to upload (ZIP format).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERBASE_TOOL_UPLOAD_SESSION_FILETool to upload files to a browser session for file input operations. Use when you need to make files available for file input fields or downloads within a browser automation session.
Input parameters
Unique identifier of the session to upload the file to
File to upload.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 30 agents privately built on Nagent that already use Browserbase.
Build on Nagent
Connect Browserbase to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Browserbase, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Browserbase is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Browserbase is connected, you configure its 19 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Browserbase steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Browserbase event fires, the agent kicks off automatically.
Every Browserbase action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Browserbase ships with 19 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Browserbase together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Browserbase-based workflows tailored to your business.