# Steel

> Steel is an open-source cloud browser infrastructure platform for AI agents. It gives your agent a real browser that can navigate pages, fill forms, solve CAPTCHAs, persist auth, and extract content from modern websites.

## When to use Steel

- An agent needs a real browser to read pages, click, type, fill forms and sign in, where an HTTP client gets blocked or sees an empty page.
- You run Playwright or Puppeteer code and want the browsers in the cloud, with proxies, CAPTCHA solving, recordings and live view.
- You need one page as Markdown, a screenshot or a PDF, without managing a browser: use the quick actions, `POST /v1/scrape`, `/v1/screenshot` and `/v1/pdf`.
- A task must stay signed in from one run to the next, with profiles, session context or stored credentials.
- You want to run the browser API yourself: Steel Browser is open source and runs in Docker.

## How agents should use Steel

- Research in Markdown. Start from the [docs sitemap](https://steel.dev/docs/sitemap.md), and fetch the one page that the task needs. Add `.md` to a docs address, or send `Accept: text/markdown`. Add `?lang=typescript`, `python`, `go` or `rust` to keep one language's code.
- Choose the interface that fits you. An agent that runs shell commands uses the Steel CLI and its `steel-browser` skill. A chat client without a shell uses the [MCP server](https://steel.dev/docs/control/mcp-server.md). Code that you write for the user uses an SDK.
- Release each session when the task ends, because an open session uses browser hours: run `steel browser stop`, call the MCP tool `session_release`, or call `sessions.release` in an SDK.
- Keep the API key in `STEEL_API_KEY`, and never print it or write it into a file.
- Ask the user before an action that spends money or changes their account, such as buying credits, creating an API key or deleting a profile.

## Agent setup

- [Install guide](https://setup.steel.dev/install.md): Set up stable Steel CLI for OpenCode, Codex, Pi, or Claude Code; approve device authorization, resume setup, and load the installed `steel-browser` skill before continuing the user's task.
- [Agent setup prompt](https://steel.dev/agent-prompt): The same short kickoff prompt used by the copy button, pointing to the canonical install guide.
- [Set up your agent](https://steel.dev/docs/get-started/agent-setup.md): Send one prompt to a coding agent and watch it browse live, or pick an agent, such as Claude Code, Codex, Cursor, OpenCode, Pi or Claude, for its own setup.
- [Connect Claude to Steel](https://steel.dev/docs/integrations/claude.md): Connect Claude on the web or in the desktop app to the Steel MCP server.
- [Write Steel code](https://steel.dev/docs/get-started/code.md): Run a first program with the SDK, and set up a coding agent with the `steel-developer` skill and these docs in Markdown.
- [Steel CLI](https://steel.dev/docs/control/cli.md): Drive a cloud browser from the terminal with `steel browser`, or get a page with `steel scrape`.
- [Skills](https://steel.dev/docs/control/skills.md): The Steel skills for coding agents, and how to install each one.
- [MCP server](https://steel.dev/docs/control/mcp-server.md): Steel's hosted MCP server at mcp.steel.dev.

## Quick reference

- Install: `npm install steel-sdk` (Node.js), `pip install steel-sdk` (Python), `go get github.com/steel-dev/sdk/go` (Go) or `cargo add steel-rs` (Rust)
- Agent CLI setup: https://setup.steel.dev/install.md
- Human-terminal CLI install: `curl -fsS https://setup.steel.dev | sh`
- Auth header: `steel-api-key: <your-key>`
- Auth env var: `STEEL_API_KEY`
- API base URL: `https://api.steel.dev`
- CDP connection: the session's `websocketUrl`, which `sessions.create` returns. It is on `wss://connect.steel.dev` and holds a token for that session, so it needs no API key.
- Every docs page has a Markdown version at its address with `.md` on the end, and a docs page answers `Accept: text/markdown`, and Claude, ChatGPT or Perplexity when they fetch it for a user, with it. Add `?lang=typescript`, `python`, `go` or `rust` to keep the code of one language.
- Each sidebar group has its full text in one file that fits in one fetch, such as [docs/llms-full/sessions.txt](https://steel.dev/docs/llms-full/sessions.txt). The Documentation section below lists them, and they take the same `?lang=`. [docs/llms-full.txt](https://steel.dev/docs/llms-full.txt) has every docs page in one file, but it is too large for one fetch.

## Start here

- [Set up your agent](https://steel.dev/docs/get-started/agent-setup.md): Send one prompt to a coding agent. The agent installs the Steel CLI, signs in and drives a cloud browser.
- [Build your first Steel automation](https://steel.dev/docs/get-started/build-your-first-steel-automation.md): Write a first Steel program with Playwright, step by step.
- [Connect Playwright to Steel](https://steel.dev/docs/integrations/playwright.md): Run the Playwright code that you already have in a Steel session.
- [Get past bot detection](https://steel.dev/docs/stealth/get-past-bot-detection.md): Choose a stealth setup from what a site does to your session.
- [Troubleshooting](https://steel.dev/docs/troubleshooting.md): Find an error or a symptom and go to its fix.
- [API reference](https://steel.dev/docs/reference/api.md): The rules that every API request follows, and a page for each group of endpoints.

## Why Steel

- **Open source**: Core browser runtime at [github.com/steel-dev/steel-browser](https://github.com/steel-dev/steel-browser). Benchmark code at [github.com/steel-dev/browserbench](https://github.com/steel-dev/browserbench).
- **Self-hostable**: Run Steel Browser in your own infrastructure [with Docker](https://steel.dev/docs/self-hosting/docker.md). No vendor lock-in.
- **Framework agnostic**: Works with Playwright and Puppeteer. SDKs for Node.js, Python, Go and Rust.
- **Production ready**: Profiles for persistent auth, CAPTCHA solving, stealth/proxy tooling, agent traces, and live session debugging.

## Key features

- Steel runs isolated cloud browser sessions through an API, CLI, and SDKs.
- Steel can return page content as HTML, markdown, screenshots, and PDFs.
- Steel can persist browser state across runs with profiles, session context, credentials, and extensions.
- Steel includes anti-bot tooling: proxies, stealth settings, CAPTCHA solving, mobile devices, and Stealth Browser on Enterprise.
- Steel includes debugging and observability tools: live view, recordings, and agent traces.
- Steel supports cloud, self-hosted, and local runtime workflows.

## SDKs

- [TypeScript SDK](https://steel.dev/docs/reference/sdks/typescript.md): `steel-sdk` on npm, for JavaScript and TypeScript projects.
- [Python SDK](https://steel.dev/docs/reference/sdks/python.md): `steel-sdk` on PyPI, for Python projects.
- [Go SDK](https://steel.dev/docs/reference/sdks/go.md): The module `github.com/steel-dev/sdk/go`.
- [Rust SDK](https://steel.dev/docs/reference/sdks/rust.md): The crate `steel-rs`.
- [Node SDK blog post](https://steel.dev/blog/steel-node-sdk): Deep dive on the Node SDK.
- [Python SDK blog post](https://steel.dev/blog/steel-python-sdk): Deep dive on the Python SDK.

## Site

- [Pricing](https://steel.dev/pricing.md): Plans, what each includes, and a comparison of them.
- [FAQ](https://steel.dev/faq.md): Answers to common questions about Steel.
- [Blog](https://steel.dev/blog.md): Guides, engineering, comparisons, product news, and company news.
- [Brand kit](https://steel.dev/brand-kit): Steel's logo, colours, and type, to download.
- [Terms of Service](https://steel.dev/terms)
- [Privacy Policy](https://steel.dev/privacy)

## Developer resources

- [Changelog](https://steel.dev/changelog): What has shipped, newest first.
- [Docs](https://steel.dev/docs.md): The front page of the Steel docs. The [docs sitemap](https://steel.dev/docs/sitemap.md) lists every page.
- [Support](https://steel.dev/docs/support.md): How to reach the Steel team, and what to send.
- [Dashboard](https://app.steel.dev): Manage API keys, usage, and sessions.
- [GitHub](https://github.com/steel-dev): Open-source repos and examples.
- [Steel Browser (OSS)](https://github.com/steel-dev/steel-browser): Open-source browser runtime and self-hosted API.
- [Benchmark Code](https://github.com/steel-dev/browserbench): Open-source remote browser benchmark.
- [Cookbook](https://github.com/steel-dev/steel-cookbook): Example projects and starters.
- [Discord](https://discord.gg/steel-dev): Community support.

## Documentation

- [Docs sitemap](https://steel.dev/docs/sitemap.md): Every docs page with a one-sentence summary and the pages to read first. Start here, and fetch the one page that the task needs.
- The full text of each sidebar group, in one file that fits in one fetch. Add `?lang=` and `typescript`, `python`, `go` or `rust` to keep the code of one language.
  - [Docs: Get started](https://steel.dev/docs/llms-full/get-started.txt): 3 pages, 33 KB
  - [Docs: Drive a browser](https://steel.dev/docs/llms-full/drive-a-browser.txt): 9 pages, 96 KB
  - [Docs: Sessions](https://steel.dev/docs/llms-full/sessions.txt): 9 pages, 100 KB
  - [Docs: Stay signed in](https://steel.dev/docs/llms-full/stay-signed-in.txt): 5 pages, 58 KB
  - [Docs: Stealth](https://steel.dev/docs/llms-full/stealth.txt): 7 pages, 81 KB
  - [Docs: Watch and debug](https://steel.dev/docs/llms-full/watch-and-debug.txt): 9 pages, 83 KB
  - [Docs: Production](https://steel.dev/docs/llms-full/production.txt): 6 pages, 59 KB
  - [Docs: Platform](https://steel.dev/docs/llms-full/platform.txt): 5 pages, 27 KB
  - [Docs: Account](https://steel.dev/docs/llms-full/account.txt): 3 pages, 25 KB
  - [Docs: Self-hosting](https://steel.dev/docs/llms-full/self-hosting.txt): 3 pages, 22 KB
  - [Docs: Help](https://steel.dev/docs/llms-full/help.txt): 3 pages, 29 KB
  - [Integrations: Agent frameworks](https://steel.dev/docs/llms-full/integrations-agent-frameworks.txt): 8 pages, 62 KB
  - [Integrations: Browser libraries](https://steel.dev/docs/llms-full/integrations-browser-libraries.txt): 2 pages, 14 KB
  - [Integrations: Coding and chat agents](https://steel.dev/docs/llms-full/integrations-coding-and-chat-agents.txt): 6 pages, 25 KB
  - [Integrations: Computer-use models](https://steel.dev/docs/llms-full/integrations-computer-use-models.txt): 3 pages, 50 KB
  - [Integrations: Platforms](https://steel.dev/docs/llms-full/integrations-platforms.txt): 2 pages, 10 KB
  - [Reference: API](https://steel.dev/docs/llms-full/reference-api.txt): 9 pages, 114 KB
  - [Reference: SDKs](https://steel.dev/docs/llms-full/reference-sdks.txt): 4 pages, 28 KB
  - [Reference: CLI, MCP and Commands](https://steel.dev/docs/llms-full/reference-cli-mcp-and-commands.txt): 3 pages, 96 KB
  - [Reference: Proxy locations, signals, errors and glossary](https://steel.dev/docs/llms-full/reference-proxy-locations-signals-errors-and-glossary.txt): 4 pages, 53 KB
- [docs/llms-full.txt](https://steel.dev/docs/llms-full.txt): Every docs page in one file, without the blog. At 1101 KB, it is too large for one fetch, so fetch the group file above that the task needs.
- [Pricing](https://steel.dev/pricing.md): Each plan, what it includes, and the usage rates.
- [FAQ](https://steel.dev/faq.md): Short answers to common questions.
- [Blog](https://steel.dev/blog.md): Every post, by category.
- [llms-full.txt](https://steel.dev/llms-full.txt): Every docs page and every blog post in full, with pricing and the FAQ.
