Head to head · Browser automation · October 2026 research run

agent-browser vs Hyperbrowser

Hyperbrowser and agent-browser score within a point of each other on agent readiness, 66.9 (B) and 66.6 (B). agent-browser leads on schema & documentation, agent ergonomics and security & auth. Both do browser automation. Hyperbrowser accepts x402. agent-browser doesn't.

Which one, for what

agent-browser B

Good for Coding agents with a shell that want short commands and compact snapshots.

Ahead on

  • Schema & documentation, 84 against 68
  • Agent ergonomics, 78 against 67
  • Security & auth, 67 against 44

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

Hyperbrowser B

Good for Agents that need a cloud browser by the minute plus cheap fetch and search, especially wallet-holding agents with no account.

Ahead on

  • Reliability, 65 against 48
  • Payments & pricing, 94 against 60
  • Maintenance & community, 79 against 70

Also in its favour

  • An agent can pay per call over x402, with no account
  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

The official MCP server's last npm release is 1.0.25 of 13 April 2025, and it isn't in the official MCP registry

Score by category

CategoryWeight this runagent-browserHyperbrowserEdge
Reliability16%204865Hyperbrowser +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28468agent-browser +16
Agent ergonomics13%16.27867agent-browser +11
Security & auth14%17.56744agent-browser +23
Payments & pricing10%12.56094Hyperbrowser +34
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87079Hyperbrowser +9
Transparency & trust7%8.86164Hyperbrowser +3
Negative events≤1500
Total66.6 · B66.9 · B

Facts side by side

Factagent-browserHyperbrowser
KindMCP serverHTTP API
VendorVercel LabsS2 Labs Inc.
Hosted endpointno (local only)https://api.hyperbrowser.ai
TransportsstdioHTTP, stdio
AuthNoneOAuth or key
PricingFreeFreemium
x402noyes
LicenceApache-2.0Proprietary service under S2 Labs' terms of service. The Node and Python SDKs and the MCP server are MIT, and HyperAgent is AGPL-3.0
Tools exposed158none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-012026-10-08
Terms last updatedno document linkedcouldn't be read
Privacy policy last updatedno document linkedcouldn't be read
Customer content may train modelscouldn't be read
Terms restrict automated accesscouldn't be read
Terms restrict benchmarkingcouldn't be read
Terms or service can change without noticecouldn't be read
Arbitration or class-action waivercouldn't be read
Popularity44k stars, 2.1M npm/wk89k npm/wk, 73k PyPI/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.

Hyperbrowser

Sessions, Fetch and Search can be bought by x402 at api.hyperbrowser.ai with USDC on Base or Solana and no account, and unit prices are public. The official MCP server was last published in April 2025, no request rate limits or SLA are published, and the privacy notice covers only the website.

Before you call either

agent-browser

  1. Run agent-browser install once after npm install -g agent-browser. It downloads Chrome for Testing
  2. Take a fresh snapshot -i after any navigation. Refs survive same-document changes only
  3. Pass --json for machine-readable results and --max-output to cap page text
  4. Set --allowed-domains, --action-policy and --content-boundaries for untrusted sites. None is on by default, and the allowlist rejects --profile, --cdp and --restore
  5. Start MCP with agent-browser mcp, and add profiles such as --tools core,network only when needed

Hyperbrowser

  1. With a wallet and no key, POST to https://api.hyperbrowser.ai/x402/session and read the PAYMENT-REQUIRED header. Sessions are prepaid for 5 to 60 minutes with no refund
  2. Save the x402 creation response. It holds the only copy of the connection tokens, and managementToken is what stops the session
  3. Stop sessions explicitly in cleanup code. Browser time bills per second until the timeout
  4. Use Fetch at $0.001 a page for static pages and keep browser sessions for pages that need interaction
  5. Add &keepAlive=true to wsEndpoint to reconnect after a CDP disconnect. Treat that URL as a secret because it carries the session token

Questions

Which is better for AI agents, agent-browser or Hyperbrowser?

Hyperbrowser and agent-browser score within a point of each other on agent readiness, 66.9 (B) and 66.6 (B). agent-browser leads on schema & documentation, agent ergonomics and security & auth.

Do agent-browser and Hyperbrowser need an API key?

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

Can an agent call agent-browser and Hyperbrowser without installing anything?

agent-browser runs on your own machine, with no hosted endpoint listed. Hyperbrowser has a hosted endpoint at https://api.hyperbrowser.ai.

Are agent-browser and Hyperbrowser open source?

agent-browser is open source (Apache-2.0). No open-source release is listed for Hyperbrowser.

Other comparisons with agent-browser or Hyperbrowser

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.