Glossary
The Steel docs use these terms with these meanings. Each entry links to the page that explains it.
Terms
| Term | Meaning |
|---|---|
| Agent traces | A timeline of what happened in a session: clicks, typing, scrolls, drags and navigations, each with the element that it targeted. See Agent traces. |
| API key | The secret that authenticates your requests to Steel. Send it in the steel-api-key header, or put it in STEEL_API_KEY for the SDKs. A key is a project key or an organization key. See API keys. |
| Bandwidth optimization | Blocking images, media, stylesheets, hosts or URL patterns, so that a session loads less data. See Reduce bandwidth. |
| Beta | A release stage. The feature works and you can use it, but its behavior and API can still change. See Release stages. |
| Browser state | What a browser remembers about the sites that it visits, such as cookies, storage and logins. A profile, a session context and credentials each carry a part of it into a new session. See Browser state. |
| CAPTCHA solving | Steel detects the CAPTCHAs in a session and solves them, at once or when you ask. See CAPTCHA solving. |
| CDP | Chrome DevTools Protocol. Playwright and Puppeteer use it to control a session's browser over a WebSocket. See CDP. |
| Command | One step of a Commands request, such as navigate, snapshot, click or fill. See Commands reference. |
| Commands | The API that drives a session's browser one step at a time: read the page as a snapshot, act on an element by its ref, and read what changed. Steel runs the commands inside the session. The Steel CLI's steel browser commands and the MCP server's page tools run on it. See Commands. |
| Computer actions | The API for mouse, keyboard and screenshot actions in a session, for computer-use models. See Computer actions. |
| Concurrency | The number of sessions that run at the same time. See Know your limits. |
| Credentials | Logins that Steel stores encrypted and fills into the sign-in forms of a session. The API never returns the stored values. See Credentials. |
| Credits | The balance that pays for usage: browser hours, proxy bandwidth, CAPTCHA solves and Quick actions. Each plan includes some, and you can buy more. See Pricing. |
| Debug URL | The debugUrl of a session: the URL of its live view, without the dashboard. You can open it in a browser or embed it in your app. See Live view. |
| Dedicated IP | An IP address that stays the same from one session to the next. See Dedicated IPs. |
| Deprecated | A release stage. Steel is removing the feature, or has removed it, and its page names what to use instead. See Release stages. |
| Enterprise | The plan with a contract. Its prices, limits and data retention are custom. See Pricing. |
| Execution | One run of a Commands request. When a run does not finish within the request, you get its result later by its ID. See Commands. |
| Experimental | A release stage for a feature or option on trial. It can change without notice, so do not depend on it in production. See Release stages. |
| Extension | A Chrome extension that you upload to Steel and install in a session with extensionIds. See Extensions. |
| Files | Session files belong to one session, in its / folder. Global files belong to your organization, and you can copy them into any session. See Files. |
| Fingerprint | The browser and device details that a site reads to recognize a browser. Steel generates one for each session. See Fingerprints. |
| Headful | A session whose browser has a visible window. Sessions are headful unless you set headless. See Create a session. |
| Headless | A session whose browser runs with no window. Set headless to true to get one. See Create a session. |
| Idempotency key | A random value in the Idempotency-Key header of a Commands request. A retry with the same key returns the stored result and does not run the commands twice. See API conventions. |
| Inactivity timeout | The time after which Steel releases a session that gets no activity, such as a CDP command, a Commands request or input from the live view. See Release idle sessions. |
| Launch | The free plan. You pay only for usage, and you get $30 of credits once. See Pricing. |
| Live view | A live video of a session's browser. You can watch it, embed it in your app, and let a person control the browser through it. See Live view. |
| Locator | A way to find an element by its role and name, its label, its text or a CSS selector, such as { "role": "button", "name": "Save" }. Unlike a ref, it works in any session. See Targets. |
| Logs | The events of a session's browser: console messages, page errors, network requests and page loads. See Logs. |
| MCP server | Steel's hosted MCP server, at https://. It gives an MCP client tools to read pages and to drive sessions. See MCP server. |
| Member | A person in an organization. See Organizations and members. |
| Metadata | Your own key-value pairs on a session, such as a job ID. You can find sessions by them. See Add metadata. |
| Namespace | A name inside a project that separates stored credentials. A session uses the credentials of its namespace, which is default unless you set another. See Projects and namespaces. |
| Organization | Your Steel account. It holds your projects, members, API keys and plan. See Organizations and members. |
| Organization key | An API key that reaches every project of the organization. The API calls its scope global. A request that creates a session, runs a Quick action, or works with profiles or credentials must name a project in projectId. See Choose a scope. |
| Profile | A saved copy of a browser: its cookies, storage, extensions, settings and user agent. A new session can start from it. See Profiles. |
| Project | A group of sessions and other resources inside an organization, for one product or environment. See Projects. |
| Project key | An API key that reaches one project. Every request with it uses that project. The API calls its scope project. See Choose a scope. |
| Quick actions | Scrape, Screenshot and PDF. Each one loads a URL and returns the result in one request, with no session to manage. The API specification calls them browser tools. See Scrape. |
| Recording | A video of a headful session that you can play after the session ends. Steel records sessions by default. See Recordings. |
| Ref | The ID of an element in a snapshot. A command uses it to act on that element. See Snapshots and refs. |
| Release | To end a session. Release a session when its task ends, so that it does not run until its timeout. See Session lifecycle. |
| Release reason | The releaseReason of a session: why it ended, such as user_requested or timeout. See Session lifecycle. |
| Release stage | How far you can rely on a feature: Beta, Experimental or Deprecated. A feature with no stage is generally available. See Release stages. |
| Scale | The plan at $250 a month plus usage. It includes $100 of credits every month, and its limits are higher than Launch's. See Pricing. |
| Session | One cloud browser that Steel runs for you. You create it, control it and release it. See Create a session. |
| Session context | The cookies, localStorage, sessionStorage and IndexedDB data of a session. You can read it from one session and pass it to a new one. See Session context. |
| Session cost | The final cost of a released session, in US dollars. See Session cost. |
| Session viewer | A session's page in the Steel dashboard, at the URL in sessionViewerUrl. It shows the live view while the session runs, and the recording, logs and agent traces after it ends. See Live view. |
| Signal | A label that Steel puts on a session after it ends, such as captcha_encountered. See Signals and Signals reference. |
| Skills | Packages of instructions that teach coding agents to use Steel. See Skills. |
| Snapshot | A text view of a page from the Commands API. It lists the elements of the page, and gives a ref to each one that you can act on. See Snapshots and refs. |
| Spending limit | A cap on what your organization spends in a month. When the organization reaches it, Steel refuses new sessions until the next month starts. See Set a spending limit. |
| Stealth Browser | Steel's own Chromium fork, for sites with strict bot detection. Some error messages call it Core Browser. See Stealth Browser. |
| Steel Browser | The open-source browser API that you can run on your own servers. See Steel Browser. |
| Steel CLI | The steel command. See CLI. |
| Steel Cloud | The service at api., where Steel runs the browsers for you. Steel Browser is the version that you run yourself. See Steel Browser. |
| Steel proxies | Residential proxies that Steel manages. Turn them on with useProxy. See Proxies. |
| Steel SDK | The client libraries of the Steel API, for TypeScript, Python, Go and Rust. The TypeScript and Python SDKs are the package steel-sdk on npm and PyPI, and Python imports it as steel. See SDKs. |
| Timeout | The longest time that a session can run. When it passes, Steel releases the session. See Set timeouts. |