Integration · Developer
AI agents for Browserbase
Give an agent a cloud web browser with Browserbase.
- Actions
- 10
- Read
- 6
- Write
- 4
Actions
What your agents can do in Browserbase
Give an agent a cloud web browser with Browserbase: search the web, fetch any page as Markdown or structured JSON, and hand a browser agent a task in plain words (fill a form, collect data across pages, check a site), then follow the run, answer its questions and read its result. Also lists and ends browser sessions.
Read 6
Look things up. Nothing changes.
Search the web
Searches the web and returns up to 10 (at most 25) results, each with title, url, author, publishedDate, image and favicon, but no page text.
Fetch a page
Fetches one web page without running its JavaScript and returns its content as Markdown (the default), the raw body, or JSON shaped by a schema you give.
Get an agent run
Reads one agent run: its status (PENDING, RUNNING, COMPLETED, FAILED, STOPPED, TIMED_OUT or PAUSED), the result once it is COMPLETED, the cause of a failure.
List agent runs
Lists agent runs, newest first, optionally by status or agent, with each run's runId, task, status, result and times.
Read an agent run's messages
Returns what an agent run said and did, oldest first: its text, its reasoning and its tool calls (search, navigate, click, type) with their results, each as message with a role and content.
List browser sessions
Lists the project's browser sessions, optionally only those with one status.
Write 4
Create, change or send.
Run a browser agent
Starts a Browserbase agent that completes a task written in plain words by searching and using a real browser: clicking, typing, filling forms and reading pages.
Answer a paused agent run
Resumes a PAUSED agent run with your answer to its question (a verification code, an approval, a choice), given as reply, and optionally more variables.
Stop an agent runDeletes data
Asks a running agent run to stop; it winds down and ends as STOPPED.
End a browser sessionDeletes data
Closes a running browser session (status REQUEST_RELEASE), which stops its billing; whatever a script or person was doing in it stops too.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Browserbase account.
What you enter
- API key
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Browserbase data
Ask a question in plain words. The agent can search the web, get an agent run or list agent runs in Browserbase, then answers with what it found.
- 02
Let an agent update Browserbase
Have the agent run a browser agent or stop an agent run in Browserbase as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Browserbase and Slack: it can search the web in Browserbase and post a summary to a Slack channel in the same run.
FAQ
Browserbase and MyDeepAgents
Can MyDeepAgents connect to Browserbase?
Yes. The Browserbase connector has 10 actions: 6 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Browserbase?
Paste an API key from your Browserbase account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Browserbase without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the 2 that delete data ask first by default.
Can I use Browserbase in workflows as well as agents?
Yes. Every Browserbase action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Browserbase to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.