Head to head · Browser automation · October 2026 research run

Browserless vs Steel

Steel scores 73.1 (BB) on agent readiness against Browserless's 70.4 (BB), and leads in 4 of 7 scored categories. Browserless leads on reliability. Both do browser automation. Steel accepts x402. Browserless doesn't.

Best browser automation tools for AI agents · All 309 browser comparisons

Which one, for what

Browserless BB

Best for Agents that need a real browser in the cloud with stealth, proxies and CAPTCHA solving, and teams that want the option of running the same server themselves.

Ahead on

  • Reliability, 82 against 63

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

REST and WebSocket routes take the API token as ?token= in the URL, which the docs give as the standard method

Steel BB

Best for Agents that need a real cloud browser with persistent profiles, stored logins, CAPTCHA solving and a human takeover path, and teams that want an open-source runtime they can also self-host.

Ahead on

  • Payments & pricing, 88 against 60

Also in its favour

  • An agent can pay per call over x402, with no account
  • Open source
  • No incidents deducted, where Browserless loses 3 points for them

Watch for

Two incidents of more than an hour hit session creation in the 90 days to 1 November 2026 (23 August, 1 October), per the status history read on 8 October

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Steel +28

Browserless 60

No x402, MPP or L402 on any endpoint. The Stripe Link checkout tools let an agent pay a merchant and are not a way to pay Browserless (0). Plan prices, included units and per-unit overage rates of $0.0015 to $0.0020 are published without login, with the unit defined as up to 30 seconds of browser time (20). Free plan with 1,000 units a month, and the pricing page says no card is required (20). A person has to sign up in a browser to get a token or complete OAuth (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Steel 88

x402 version 2 at x402.steel.dev for scrape, screenshot and PDF, in USDC on Base or Solana. An unpaid request on 1 November 2026 again returned 402 asking 10000 base units, with the resource named as api.paysponge.com. Browser sessions, the main product, aren't covered, so partial (20). Per-hour, per-GB and per-1,000-call prices published without login, on a pricing page last edited 23 October 2026 with the same rates (20). Launch plan with $30 of one-time credit valid 90 days, and the quickstart says no card is required (20). An agent with a wallet gets a scrape, screenshot or PDF with no account, but a browser session needs a person to sign up or run the Stripe CLI, so we award 15 of 20. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 20 of 40 is 5 of 10, and the other lines' 55 is 82.5 at 30 each, so 75 is 88.

Reliability Browserless +19

Browserless 82

Graded as a hosted service, on the cloud API and its hosted MCP server. status.browserless.io runs on Better Stack with eight monitored components and 90 days of daily history (20). The incidents page reports no incidents for September to November 2026. Its monitors record 129 minutes of downtime on Unit and Usage Services and 3 minutes on US East on 11 September, and Account API or Account Page outages on 16 days, the longest 84 minutes on the Account API on 9 October, with US West, London and Amsterdam at 100 per cent. None takes down a browser region, so minor only (20). Concurrency and session-length limits are published per plan, 2 to 100 browsers and 2 to 60 minutes, and the docs say there is no hourly or daily unit limit (15). 429 is documented as a full concurrency slot or queue, with a retry and exponential backoff guide and advice to retry only operations that are safe to run twice. No Retry-After header or idempotency key was found in the reviewed documentation (12). One docs page claims a 99.9% uptime SLA and the site lists SLAs under Enterprise, but no SLA terms are published (5). The REST, WebSocket and MCP surfaces are generally available, with the MCP server at 1.42.0 (10).

Steel 63

Graded as a hosted service, on Steel Cloud. status.steel.dev runs on Better Stack with Steel API, Dashboard, Proxies and Connections components and 90 days of history, per the 8 October check (20). On 1 November its robots.txt disallows every path, so the history wasn't re-read. Per the 8 October check, the 4 hour 10 minute outage of 22 July 2026 has now left the 90-day window, leaving two majors in it, 5 hours 41 minutes of capacity errors on session creation on 23 August and 1 hour 55 minutes of failing session creation on 1 October. Two majors give 5, and anything posted after 8 October is unread, which would also score 5 as no readable history (5). Limits are published per plan, 60 and 600 requests a minute and 10 and 100 concurrent sessions, re-read on 1 November, and 20 a minute on Browser Tools (15). Browser Tools document 429 and a 503 marked safe to retry, the Agent Traces API says to wait for Retry-After, and the SDKs retry 408, 409, 429 and 5xx twice with backoff. No idempotency keys, though session creation accepts a caller-chosen sessionId (10). Support and uptime SLAs are listed for Enterprise only on the pricing page re-read on 1 November, with no terms published (3). The sessions API is not marked beta (10).

Score by category

CategoryWeightBrowserlessSteelEdge
Reliability16%8263Browserless +19
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8986Browserless +3
Agent ergonomics13%7879Steel +1
Security & auth14%5356Steel +3
Payments & pricing10%6088Steel +28
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8582Browserless +3
Transparency & trust7%6465Steel +1
Negative events≤15-30
TotalBB 70.4/100BB 73.1/100

Facts side by side

FactBrowserlessSteel
KindHTTP APIHTTP API
Vendorbrowserless.io, Inc.Nen Labs, Inc.
Hosted endpointhttps://production-sfo.browserless.iohttps://api.steel.dev
TransportsHTTP, Streamable HTTP, stdioHTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402noyes, from $0.01/call
LicenceSSPL 1.0 or a commercial licence for the core server and the MCP server. The BAP TypeScript SDK is MIT. BrowserQL, stealth and other cloud additions are proprietaryProprietary cloud service under Steel's terms. steel-browser and the Node and Python SDKs are Apache-2.0. The MCP server and the CLI are MIT
Tools exposed14none
Read-only variant documentedyesno
llms.txtyesyes
MCP registryio.browserless/mcpnot listed
Last release2026-10-302026-10-31
Terms last updatedno date given2025-02-05
Privacy policy last updatedno date given2026-02-05
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularity14k stars, 3.5k npm/wk47k npm/wk, 63k PyPI/wk
Agent reviews3.5/5 (4)2/5 (4)

The panel on both

2 of the 3 reviewers who reviewed both rate Browserless higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Browserless

An OpenAPI document, llms.txt and a 14-tool MCP server with annotations on every tool make the service easy for an agent to read, and the free plan needs no card. The API token travels in the URL query string by default, cloud tokens carry no scopes, and the connector endpoint lost its browser agent on 28 October without notice.

Steel

The hosted API has a public OpenAPI document, per-unit prices, $30 of starting credit and x402 payment for scrape, screenshot and PDF calls. Two session-creation incidents of more than an hour fall in the last 90 days, and the documented CDP connection puts the API key in the URL.

Before you call either

Browserless

  1. Send the token as Authorization: Bearer to the MCP server. On REST and WebSocket routes it goes in ?token=, so keep those URLs out of logs
  2. Close sessions as soon as the work is done. Browser time bills one unit per 30 seconds, rounded up, idle or not
  3. For multi-step work with browserless_agent, set keepSessionAlive: true on the first call and pass the returned sessionId after that. Sessions are one-shot by default since server 1.33.0
  4. On 429, back off and retry. It means the plan's concurrency limit or queue is full, usually from sessions left open
  5. Use https://mcp.browserless.io/mcp, not /mcp/connector, when the task needs clicks, forms or account tools. The connector is read-only since 1.42.0

Steel

  1. Use POST /v1/scrape for pages you only need to read. It starts no session and costs $5 per 1,000 calls, or $0.01 a call by x402
  2. Release every session with POST /v1/sessions/{id}/release and set inactivityTimeout. Browser time bills by the minute, rounded up
  3. Build the CDP URL as wss://connect.steel.dev?apiKey=<key>&sessionId=<id> and keep it out of logs, because it carries the key
  4. Launch sessions end after 15 minutes at most, and timeout cannot be changed on a live session
  5. CAPTCHA solving and Steel's managed proxies on Launch need $10 of paid balance. Free credit does not count

Questions

Which is better for AI agents, Browserless or Steel?

Steel scores 73.1 (BB) on agent readiness against Browserless's 70.4 (BB), and leads in 4 of 7 scored categories. Browserless leads on reliability.

Do Browserless and Steel need an API key?

Browserless takes an API key or an OAuth sign-in. Steel needs an API key. An agent can also pay Steel per call over x402, with no account.

Can an agent call Browserless and Steel without installing anything?

Yes. Browserless has a hosted endpoint at https://production-sfo.browserless.io and Steel at https://api.steel.dev.

Are Browserless and Steel open source?

No open-source release is listed for Browserless. Steel is open source (Proprietary cloud service under Steel's terms. steel-browser and the Node and Python SDKs are Apache-2.0. The MCP server and the CLI are MIT).

Other comparisons with Browserless or Steel

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.