Skip to main content
AgentsUse

Browser Automation

Steel

An open-source browser API for AI agents and apps: a batteries-included browser sandbox you can self-host or run as Steel Cloud.

Official siteDocumentationRepository
open_sourceApache-2.0Checked 2026-10-07Source verified

Quick decision

Best for
Agents that need isolated, disposable browser sessions on demand Teams that want a browser control API they can self-host Computer-use agents that need a managed Chrome to drive
Not ideal for
Workflows that need the agent loop, recovery, and planning built in Static page fetching where a browser is overkill
Pricing model
The browser API is open source under Apache-2.0; Steel Cloud is the hosted version, and current cloud pricing is published on the Steel site.
Deployment
cloud. self_hosted.
Authentication
api_key
Review state
Source verified. Facts checked 2026-10-07. Not locally tested by AgentsUse.

What it does

Steel Browser is described by its maintainers as an open-source browser API for AI agents and apps, a batteries-included browser sandbox that manages sessions, browser control over a full HTTP API, and the production plumbing around running browsers. The Steel project publishes the open-source steel-browser repository under Apache-2.0, and Steel Cloud is the hosted version of the same API.

The API revolves around sessions: create a browser session, connect your agent framework or CDP client to it, run the task, and release the session. Official SDKs in TypeScript, Python, Rust, and Go wrap the API, and the documentation shows pairings with computer-use agents and frameworks such as Claude Computer Use, OpenAI Computer Use, Browser Use, and CrewAI.

Because the browser service is open source, a team can self-host the sandbox and move to Steel Cloud when operating browsers stops being where it wants to spend time. What Steel does not add is agent planning: the model and loop still come from your framework.

Verified capabilities

Core capability

  • Sessions API Source verified

    API endpoints for creating, managing, and releasing Steel browser sessions.

  • CDP-compatible connection Source verified

    Agents connect to a running session and control the browser, including documented pairings with computer-use models and agent frameworks.

  • Official SDKs Source verified

    Steel publishes TypeScript, Python, Rust, and Go SDKs for building applications on the API.

  • Self-hostable browser service Source verified

    The steel-browser repository is the open-source browser API itself, so the sandbox can run on your own infrastructure.

  • Framework pairings Source verified

    Documentation covers using Steel with Claude Computer Use, OpenAI Computer Use, Gemini Computer Use, Browser Use, Magnitude, and CrewAI.

  • Steel CLI and agent skill Source verified

    The docs lead with installing the Steel CLI and the steel-browser skill so a coding agent can control a browser.

Quick start

Create a Steel session from Python

Self-hosted Steel runs the same API without a cloud key.

Create a Steel session from Python
pip install steel-sdk

from steel import Steel

client = Steel(steel_api_key="YOUR_API_KEY")
session = client.sessions.create()
print(session.id)

Source: https://github.com/steel-dev/steel-browser. Examples use placeholders only. Never paste a real key into a profile, config file you share, or a ticket.

MCP support: Steel is commonly driven through its API and CDP by MCP-capable agents; check current docs for the supported server setup.

Works with

Frameworks

CrewAI, Browser Use, Claude Computer Use, OpenAI Computer Use

SDKs and packages

TypeScript, Python, Rust, Go

Works with

Any CDP client

Only sourced support is listed. A missing framework means AgentsUse has not verified it yet, not that it cannot work.

Health and maintenance

GitHub stars

7,748

Checked 2026-10-07

GitHub forks

989

Checked 2026-10-07

License
Open source, Apache-2.0
Maintainer
Steel

GitHub API repository counts and Apache-2.0 license for steel-dev/steel-browser, fetched 2026-10-07.

Pricing and license

The browser API is open source under Apache-2.0; Steel Cloud is the hosted version, and current cloud pricing is published on the Steel site.

Official pricing or docs →

Limitations and safety

  • Provides the browser session layer, not agent planning, retries, or task evaluation.
  • Self-hosting means operating browser fleets, updates, and abuse controls yourself.
Safety

Browser and data tools can read pages, fill forms, and download files. Start with a test account or read-only access, keep credentials in environment variables, and review agent actions before connecting anything that can spend money, send messages, or delete data.

Alternatives to Steel

Browserbase

Larger hosted browser platform with search and fetch APIs alongside sessions

Tradeoff: Its profile lists its own limits, pricing, and verification details for a side-by-side read.

Playwright

Drive browsers directly with a mature automation library and no session service

Tradeoff: Its profile lists its own limits, pricing, and verification details for a side-by-side read.

Browser Use

Agent-native planning on top of the browser

Tradeoff: Its profile lists its own limits, pricing, and verification details for a side-by-side read.

Common questions

What does Steel do for an AI agent?

An open-source browser API for AI agents and apps: a batteries-included browser sandbox you can self-host or run as Steel Cloud.

Is Steel open source?

Yes. This profile records the license as Apache-2.0 from the official repository.

Does Steel support MCP?

Steel is commonly driven through its API and CDP by MCP-capable agents; check current docs for the supported server setup.

Sources and freshness

Last checked 2026-10-07. Verification label: source verified, which means public claims trace to the sources above. It does not mean AgentsUse ran the tool. Spotted an error? Send a correction. Back to the tools directory.