Head to head · Browser automation · October 2026 research run
Notte vs Steel
Steel scores 70.4 (BB) on agent readiness against Notte's 63.2 (B), and leads in 4 of 7 scored categories. Both do browser automation. Steel accepts x402. Notte doesn't.
Which one, for what
Notte B
Good for Teams that want hosted browsers together with agents, vaults for logins, personas with mailboxes and scheduled browser functions behind one key.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
status.notte.cc shows the Scrape API down on 15 of 90 days (about 6 hours in total) and CAPTCHA solving at 88.9 per cent availability
Steel BB
Good 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
- Schema & documentation, 86 against 74
- Payments & pricing, 75 against 40
Also in its favour
- Agent-ready, a grade of BB or better
- An agent can pay per call over x402, with no account
- Runs on your own machine
- Open source
Watch for
Three incidents of more than an hour hit the API or session creation in the 90 days to 8 October 2026, the longest 5 hours 41 minutes
Score by category
| Category | Weight this run | Notte | Steel | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 58 | 58 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 74 | 86 | Steel +12 |
| Agent ergonomics | 13%16.2 | 75 | 79 | Steel +4 |
| Security & auth | 14%17.5 | 56 | 56 | even |
| Payments & pricing | 10%12.5 | 40 | 75 | Steel +35 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 83 | 82 | Notte +1 |
| Transparency & trust | 7%8.8 | 61 | 64 | Steel +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 63.2 · B | 70.4 · BB |
Facts side by side
| Fact | Notte | Steel |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Notte Labs Inc. | Nen Labs, Inc. |
| Hosted endpoint | https://api.notte.cc | https://api.steel.dev |
| Transports | HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | yes, from $0.01/call |
| Licence | Proprietary hosted service under Notte's terms of service. The core repository is SSPL-1.0 and the Node SDK is MIT | 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 |
| Tools exposed | 8 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-07 | 2026-10-02 |
| Terms last updated | couldn't be read | 2025-02-05 |
| Privacy policy last updated | couldn't be read | 2026-02-05 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 1.3k npm/wk, 5.1k PyPI/wk | 47k npm/wk, 63k PyPI/wk |
Verdicts
Notte
Notte publishes an OpenAPI 3.1 contract for 100 operations, a hosted MCP server with eight tools and OAuth, and a free plan with $10 of credits and no card. Its status page records about six hours of Scrape API downtime in 90 days, and a bot check blocked our read of the terms and privacy policy.
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. The status page records three API or session-creation incidents of more than an hour in 90 days, and the documented CDP connection puts the API key in the URL.
Before you call either
Notte
- Send
Authorization: Bearer $NOTTE_API_KEYto https://api.notte.cc. A person creates the key in the console at console.notte.cc first - Stop every session when the task ends. Sessions close after 3 idle minutes or 15 minutes in total by default, and the Free plan caps a session at 15 minutes
- Use https://api.notte.cc/mcp for browser work. Function and agent administration tools are only on https://api.notte.cc/mcp/full
- Back off on 429 and on 529, which means the cluster has too many sessions. The SDKs do not retry rate limits for you
- Download session replays within 24 hours. The recordings page says they are deleted after that
Steel
- Use
POST /v1/scrapefor pages you only need to read. It starts no session and costs $5 per 1,000 calls, or $0.01 a call by x402 - Release every session with
POST /v1/sessions/{id}/releaseand setinactivityTimeout. Browser time bills by the minute, rounded up - Build the CDP URL as
wss://connect.steel.dev?apiKey=<key>&sessionId=<id>and keep it out of logs, because it carries the key - Launch sessions end after 15 minutes at most, and
timeoutcannot be changed on a live session - 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, Notte or Steel?
Steel scores 70.4 (BB) on agent readiness against Notte's 63.2 (B), and leads in 4 of 7 scored categories.
Do Notte and Steel need an API key?
Notte 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 Notte and Steel without installing anything?
Yes. Notte has a hosted endpoint at https://api.notte.cc and Steel at https://api.steel.dev.
Are Notte and Steel open source?
No open-source release is listed for Notte. 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 Notte or Steel
- Airtop vs Notte
- Airtop vs Steel
- Anchor Browser vs Notte
- Anchor Browser vs Steel
- Browser Use vs Notte
- Browser Use vs Steel
- Browserless vs Notte
- Browserless vs Steel
- Chrome DevTools MCP vs Notte
- Chrome DevTools MCP vs Steel
- Hyperbrowser vs Notte
- Hyperbrowser vs Steel
- Notte vs Playwright MCP
- Notte vs Puppeteer (archived MCP reference server)
- Notte vs Skyvern
- Playwright MCP vs Steel
- Puppeteer (archived MCP reference server) vs Steel
- Skyvern vs Steel
- Browserbase vs Notte
- Browserbase vs Steel
Machine-readable
- This page as Markdown
/compare/notte-vs-steel.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/notte.json·/api/v1/tools/steel.json - From a terminal
anchor compare notte steel(the CLI) - Over MCP
compare_tools {"a": "notte", "b": "steel"}at/mcp, no key