Head to head · Browser automation · October 2026 research run
agent-browser vs Browserless
Browserless scores 70.4 (BB) on agent readiness against agent-browser's 66.6 (B), and leads in 4 of 7 scored categories. agent-browser leads on security & auth and payments & pricing. Both do browser automation.
Which one, for what
Good for Coding agents with a shell that want short commands and compact snapshots.
Ahead on
- Security & auth, 67 against 53
- Payments & pricing, 60 against 40
Also in its favour
- No key needed to call it
- Open source
Watch for
The ten most recent CI runs on main, 1 to 8 October 2026, all concluded in failure. In the newest, Windows Rust tests and native end-to-end tests failed
Browserless BB
Good 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 48
- Schema & documentation, 89 against 84
- Maintenance & community, 82 against 70
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
REST and WebSocket routes take the API token as ?token= in the URL, which the docs give as the standard method
Score by category
| Category | Weight this run | agent-browser | Browserless | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 48 | 82 | Browserless +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 89 | Browserless +5 |
| Agent ergonomics | 13%16.2 | 78 | 78 | even |
| Security & auth | 14%17.5 | 67 | 53 | agent-browser +14 |
| Payments & pricing | 10%12.5 | 60 | 40 | agent-browser +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 70 | 82 | Browserless +12 |
| Transparency & trust | 7%8.8 | 61 | 62 | Browserless +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 66.6 · B | 70.4 · BB |
Facts side by side
| Fact | agent-browser | Browserless |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Vercel Labs | browserless.io, Inc. |
| Hosted endpoint | no (local only) | https://production-sfo.browserless.io |
| Transports | stdio | HTTP, Streamable HTTP, stdio |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | SSPL 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 proprietary |
| Tools exposed | 158 | 14 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-01 | 2026-10-05 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | yes | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | yes | |
| Arbitration or class-action waiver | not found in the text | |
| Popularity | 44k stars, 2.1M npm/wk | 14k stars, 3.5k npm/wk |
Verdicts
agent-browser
Snapshots with element refs, a 29-tool default MCP profile and opt-in domain allowlists, action policies and content boundary markers suit agent use. The project is at 0.38.2 with no stable release, the ten most recent CI runs on main failed between 1 and 8 October 2026, and every security control is off by default.
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 no machine payment route exists.
Before you call either
agent-browser
- Run
agent-browser installonce afternpm install -g agent-browser. It downloads Chrome for Testing - Take a fresh
snapshot -iafter any navigation. Refs survive same-document changes only - Pass
--jsonfor machine-readable results and--max-outputto cap page text - Set
--allowed-domains,--action-policyand--content-boundariesfor untrusted sites. None is on by default, and the allowlist rejects--profile,--cdpand--restore - Start MCP with
agent-browser mcp, and add profiles such as--tools core,networkonly when needed
Browserless
- Send the token as
Authorization: Bearerto the MCP server. On REST and WebSocket routes it goes in?token=, so keep those URLs out of logs - Close sessions as soon as the work is done. Browser time bills one unit per 30 seconds, rounded up, idle or not
- For multi-step work with
browserless_agent, setkeepSessionAlive: trueon the first call and pass the returnedsessionIdafter that. Sessions are one-shot by default since server 1.33.0 - On 429, back off and retry. It means the plan's concurrency limit or queue is full, usually from sessions left open
- Match the path to the protocol. Use
/chromiumfor CDP clients and/chromium/playwrightonly forplaywright.connect()
Questions
Which is better for AI agents, agent-browser or Browserless?
Browserless scores 70.4 (BB) on agent readiness against agent-browser's 66.6 (B), and leads in 4 of 7 scored categories. agent-browser leads on security & auth and payments & pricing.
Do agent-browser and Browserless need an API key?
agent-browser needs no key. Browserless takes an API key or an OAuth sign-in.
Can an agent call agent-browser and Browserless without installing anything?
agent-browser runs on your own machine, with no hosted endpoint listed. Browserless has a hosted endpoint at https://production-sfo.browserless.io.
Are agent-browser and Browserless open source?
agent-browser is open source (Apache-2.0). No open-source release is listed for Browserless.
Other comparisons with agent-browser or Browserless
- agent-browser vs Airtop
- agent-browser vs Anchor Browser
- agent-browser vs Browser Use
- agent-browser vs Browserbase
- agent-browser vs Chrome DevTools MCP
- agent-browser vs Hyperbrowser
- agent-browser vs Notte
- agent-browser vs Playwright MCP
- agent-browser vs Puppeteer (archived MCP reference server)
- agent-browser vs Skyvern
- agent-browser vs Steel
- agent-browser vs TinyFish
- Airtop vs Browserless
- Anchor Browser vs Browserless
- Browser Use vs Browserless
- Browserless vs Chrome DevTools MCP
- Browserless vs Hyperbrowser
- Browserless vs Notte
- Browserless vs Playwright MCP
- Browserless vs Puppeteer (archived MCP reference server)
- Browserless vs Skyvern
- Browserless vs Steel
- Browserless vs TinyFish
- Browserbase vs Browserless
Machine-readable
- This page as Markdown
/compare/agent-browser-vs-browserless.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/agent-browser.json·/api/v1/tools/browserless.json - From a terminal
anchor compare agent-browser browserless(the CLI) - Over MCP
compare_tools {"a": "agent-browser", "b": "browserless"}at/mcp, no key