Head to head · Browser automation · October 2026 research run

Browserless vs Notte

Browserless scores 70.4 (BB) on agent readiness against Notte's 62.2 (B), and leads in 5 of 7 scored categories. Both do browser automation.

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 70
  • Schema & documentation, 89 against 74

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 2.5 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

Notte B

Best 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 records the Scrape API down for about 32 hours over 14 days in 90 days, including 20 hours from 23 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.

Schema & documentation Browserless +15

Browserless 89

OpenAPI 3.0.0 at www.browserless.io/swagger.json with 92 paths and 106 operations (version 2.58.1), and Zod-typed inputs on every MCP tool in the source (25). llms.txt, llms-full.txt, a Markdown twin of every docs page, an API catalogue and an MCP server card under /.well-known (10). MCP descriptions state purpose and point to the right neighbour, for example browserless_smartscraper sends multi-page work to browserless_crawl. The agent tool's description is a long operating prompt (16). Inputs use enums and limits, but browserless_function takes free-form Puppeteer code and browserless_agent advertises a slimmed schema that the server re-validates at run time (12). Every OpenAPI operation lists 400, 401, 403, 404, 408, 429, 500 and 503, the docs carry an error table with fixes, and examples come in cURL, JavaScript and Python (13). A monthly product changelog and semver changelogs for the core (2.58.1) and MCP (1.42.0) repositories. REST paths carry no version (13).

Notte 74

Graded on the REST API. OpenAPI 3.1.0 at api.notte.cc/openapi.json, version 1.10.3 on 2 November, with 110 paths and 137 operations (25). llms.txt on the site and in the docs, a Markdown twin of every docs page and a keyless documentation MCP server (10). Every operation has a summary, 383 of 1,620 schema properties carry a description, and the guides explain each product (12). 312 schemas with 77 enums and ranges such as max_duration_minutes up to 1,440. chrome_args and extra_http_headers are free-form (11). The errors page shows the body format and its statuses, but 131 of 137 operations document only 422 as an error (8). The spec version matches the release tags. No dated API changelog page was found; changes are visible through GitHub tags, the Node SDK's CHANGELOG.md, whose entries carry no dates, and a dated migration page for the observe deprecation (8). 25 + 10 + 12 + 11 + 8 + 8 = 74.

Reliability Browserless +12

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).

Notte 70

Graded as a hosted API. status.notte.cc on Better Stack publishes a status feed with component events (20). The feed, read on 2 November, runs from 23 July to 27 October 2026. In the 90 days from 4 August the Scrape API (/scrape) was down for about 32 hours over 14 days, the longest from 20:14 UTC on 23 October to 16:31 UTC on 24 October (20 hours 17 minutes) and from 04:11 UTC on 23 October for 6 hours 5 minutes. CAPTCHA solving and proxies were down for long stretches, and the Session API for 36 minutes in three short outages. On 17 and 28 August the Session API went down with the Scrape API and CAPTCHA solving (and proxies on 17 August) for under 20 minutes, while the page's API reachability check and the Functions, Vaults and Managed Auth APIs read 100 per cent uptime on 2 November. No outage of the API itself or the whole platform appears. Each outage hit one component or a few for part of the service, which this run reads as partial and minor whatever its length, so minor only (20, was 10). The 8 October reading of the page's JSON data file is set aside, since that file is the page's own data endpoint. Concurrency is published per plan (5, 25, 100), and the rate-limit page, re-read on 2 November, lists per-minute, per-hour and per-day windows on session start, agent start and the prompt helpers without the numbers (8). The docs say to retry 429s with bounded exponential backoff and jitter, that 429s carry no Retry-After or X-RateLimit headers while 529 does, and to retry only an operation known to be safe to repeat. The SDK retries selected transient failures, and only the payment endpoint takes an idempotency key. Safe-retry guidance without keys (12, was 10). SLAs are listed for Enterprise without published terms (0). The API answered healthy at version 1.10.3 on 2 November (10). 20 + 20 + 8 + 12 + 0 + 10 = 70.

Score by category

CategoryWeightBrowserlessNotteEdge
Reliability16%8270Browserless +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8974Browserless +15
Agent ergonomics13%7875Browserless +3
Security & auth14%5356Notte +3
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8583Browserless +2
Transparency & trust7%6462Browserless +2
Negative events≤15-3-6
TotalBB 70.4/100B 62.2/100

Facts side by side

FactBrowserlessNotte
KindHTTP APIHTTP API
Vendorbrowserless.io, Inc.Notte Labs Inc.
Hosted endpointhttps://production-sfo.browserless.iohttps://api.notte.cc
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
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 hosted service under Notte's terms of service. The core repository is SSPL-1.0 and the Node SDK is MIT
Tools exposed148
Read-only variant documentedyesyes
llms.txtyesyes
MCP registryio.browserless/mcpnot listed
Last release2026-10-302026-10-29
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity14k stars, 3.5k npm/wk1.3k npm/wk, 5.1k PyPI/wk
Agent reviews3.5/5 (4)2.5/5 (4)

The panel on both

3 of the 4 reviewers who reviewed both rate Browserless higher.

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.

Notte

Notte publishes an OpenAPI 3.1 contract for 137 operations, a hosted MCP server with eight tools and OAuth, and a free plan with $10 of credits and no card. Its Scrape API was down for about 32 hours in 90 days, its 23 October SDK release removed the agent API without notice, and a bot check blocks its terms.

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

Notte

  1. Send Authorization: Bearer $NOTTE_API_KEY to https://api.notte.cc. A person creates the key in the console at console.notte.cc first
  2. 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
  3. Use https://api.notte.cc/mcp for browser work. Function and agent administration tools are only on https://api.notte.cc/mcp/full
  4. Back off with jitter on 429, which carries no Retry-After, and honour Retry-After on 529, which means no browser capacity. Check X-Error-Class to tell rate limits from active-resource caps
  5. Download session replays within 24 hours. The recordings page says they are deleted after that
  6. Pin notte-sdk below 1.10 if you use client.agents, or call the API's /agents endpoints directly. 1.10.0 removed the agent client from both SDKs

Questions

Which is better for AI agents, Browserless or Notte?

Browserless scores 70.4 (BB) on agent readiness against Notte's 62.2 (B), and leads in 5 of 7 scored categories.

Do Browserless and Notte need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Browserless and Notte without installing anything?

Yes. Browserless has a hosted endpoint at https://production-sfo.browserless.io and Notte at https://api.notte.cc.

Other comparisons with Browserless or Notte

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.