Browser Use integration

AI & Machine Learning · 25 actions · API key auth

AI-powered cloud browser automation via the Browser Use API

Put Browser Use to work View Browser Use integration docs

Overview

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

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

Ask the assistant

Drive Browser Use in plain English

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

Create an agent session, dispatch a task, or dispatch a follow-up task to an existing idle session
resolves tocreate_session
Find the session I describe and remove it
resolves toget_sessiondelete_session
Update a standalone browser session
resolves toupdate_browser_session
Show me the sessions that match what I describe
resolves tolist_sessions

Use cases

What you can automate with Browser Use

Find the right session and remove it in one promptget_sessiondelete_session
Pull a list of session messages for a reportlist_session_messages
Create a browser session straight from a requestcreate_browser_session
Look up a profile on demandget_profile
Remove a workspace you no longer needdelete_workspace
Upload a workspace file from a requestupload_workspace_files

At a glance

Browser Use integration at a glance

VendorBrowser Use

CategoryAI & Machine Learning

Actions available25

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 25 Browser Use actions

Sessions5

create_session

Create an agent session, dispatch a task, or dispatch a follow-up task to an existing idle session

get_session

Get the current state, output, live URL, screenshot URL, and cost details for an agent session

list_sessions

List Browser Use agent sessions for the authenticated project

delete_session

Delete an agent session

stop_session

Stop the current task or stop the entire Browser Use agent session

Session Messages1

list_session_messages

List messages from a Browser Use agent session, including reasoning, tool calls, browser actions, screenshots, and results

Browser Sessions4

create_browser_session

Create a standalone browser session for direct browser control through CDP

get_browser_session

Get details for a standalone browser session, including live URL, CDP URL, status, timeout, and cost fields

list_browser_sessions

List standalone browser sessions for direct browser control via CDP

update_browser_session

Update a standalone browser session. Currently supports the stop action

Profiles5

create_profile

Create a profile to preserve cookies, local storage, and login state across sessions

get_profile

Get a Browser Use profile by ID

list_profiles

List Browser Use profiles, optionally searching by profile name or user ID

delete_profile

Delete a Browser Use profile and its persisted browser state

update_profile

Update a Browser Use profile name or user ID

Workspaces5

create_workspace

Create a workspace for persistent shared file storage across sessions

get_workspace

Get a Browser Use workspace by ID

list_workspaces

List Browser Use workspaces for persistent shared file storage across sessions

delete_workspace

Delete a Browser Use workspace and its stored files. This cannot be undone

update_workspace

Update a Browser Use workspace name

Workspace Sizes1

get_workspace_size

Get storage usage for a Browser Use workspace

Workspace Files3

list_workspace_files

List files and folders in a Browser Use workspace, optionally returning presigned download URLs

delete_workspace_file

Delete a file from a Browser Use workspace

upload_workspace_files

Create presigned upload URLs for workspace files

Account Billings1

get_account_billing

Get account billing details for the authenticated project

See full parameters and response schemas in the Browser Use integration docs

Two ways

Two ways to use Browser Use in ModuleX

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

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

Security

Connecting Browser Use

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

Step-by-step setup in the Browser Use docs

Pairs well with Browser Use

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

Amazon Alexa2 actions

FAQ

Browser Use + ModuleX FAQ

A ModuleX agent can run any of Browser Use's 25 actions — across sessions, session messages, browser sessions and profiles — from a plain-English request, using your organization's own Browser Use credentials.

No. The agent selects the right Browser Use 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 Browser Use API key, stored encrypted and scoped to your organization.

25, spanning sessions, session messages, browser sessions and profiles.

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

Put Browser Use to work in ModuleX.

Connect Browser Use once with your own credentials and let your agent run all 25 actions on demand.

Put Browser Use to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →