Head to head · Browser automation · October 2026 research run
Hyperbrowser vs TinyFish
TinyFish and Hyperbrowser score within a point of each other on agent readiness, 67.7 (B) and 66.9 (B). Hyperbrowser leads on reliability, payments & pricing and transparency & trust. Both do browser automation. Hyperbrowser accepts x402. TinyFish doesn't.
Which one, for what
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 60
- Payments & pricing, 94 against 55
- Transparency & trust, 64 against 59
Also in its favour
- An agent can pay per call over x402, with no account
- Runs on your own machine
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
TinyFish B
Good for Agents that want one account for a goal-driven web agent, a raw CDP browser, and free search and fetch.
Ahead on
- Schema & documentation, 85 against 68
- Agent ergonomics, 79 against 67
- Security & auth, 57 against 44
Watch for
The terms of 17 August 2026 allow Tiny Fish to train and improve its models on customer data. No opt-out was found in the reviewed pages
Score by category
| Category | Weight this run | Hyperbrowser | TinyFish | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 60 | Hyperbrowser +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 68 | 85 | TinyFish +17 |
| Agent ergonomics | 13%16.2 | 67 | 79 | TinyFish +12 |
| Security & auth | 14%17.5 | 44 | 57 | TinyFish +13 |
| Payments & pricing | 10%12.5 | 94 | 55 | Hyperbrowser +39 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 79 | 80 | TinyFish +1 |
| Transparency & trust | 7%8.8 | 64 | 59 | Hyperbrowser +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 66.9 · B | 67.7 · B |
Facts side by side
| Fact | Hyperbrowser | TinyFish |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | S2 Labs Inc. | Tiny Fish, Inc. |
| Hosted endpoint | https://api.hyperbrowser.ai | https://agent.tinyfish.ai |
| Transports | HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | yes | no |
| Licence | Proprietary service under S2 Labs' terms of service. The Node and Python SDKs and the MCP server are MIT, and HyperAgent is AGPL-3.0 | Proprietary service under Tiny Fish's terms of service. The MCP proxy @tiny-fish/mcp and the cookbook are MIT. The SDK packages state no licence in npm or PyPI metadata |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | ai.tinyfish.agent/web-agent |
| Last release | 2026-10-08 | 2026-10-07 |
| Terms last updated | couldn't be read | 2026-08-17 |
| Privacy policy last updated | couldn't be read | 2025-12-14 |
| Customer content may train models | couldn't be read | yes |
| 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 | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 89k npm/wk, 73k PyPI/wk | 5.7k npm/wk, 6.5k PyPI/wk |
Verdicts
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.
TinyFish
OpenAPI documents are published for five APIs, errors carry typed codes and request IDs, and Search and Fetch are free within daily allowances. The terms let Tiny Fish train its models on customer data, run creation takes no idempotency keys, and the status page shows an hour or more of downtime on several days for the Browser and Search APIs.
Before you call either
Hyperbrowser
- With a wallet and no key, POST to https://api.hyperbrowser.ai/x402/session and read the
PAYMENT-REQUIREDheader. Sessions are prepaid for 5 to 60 minutes with no refund - Save the x402 creation response. It holds the only copy of the connection tokens, and
managementTokenis what stops the session - Stop sessions explicitly in cleanup code. Browser time bills per second until the timeout
- Use Fetch at $0.001 a page for static pages and keep browser sessions for pages that need interaction
- Add
&keepAlive=truetowsEndpointto reconnect after a CDP disconnect. Treat that URL as a secret because it carries the session token
TinyFish
- Check
resultas well asstatus. A run can beCOMPLETEDwhile the goal failed, withresult.statusset tofailure - Don't retry
POST /v1/automation/runblindly after a timeout. There are no idempotency keys, so list runs first to avoid duplicates - Use
/v1/automation/run-asyncor/run-ssewhen a run may need cancelling. Runs started with the synchronous endpoint can't be cancelled - Allow 60 seconds for Browser session creation, connect Playwright to
cdp_url(notbase_url), andDELETEthe session when done because billing is per minute - Never put passwords in
goal, which is logged. Passuse_vault: truewithcredential_item_ids, oruse_profile: truefor saved login state
Questions
Which is better for AI agents, Hyperbrowser or TinyFish?
TinyFish and Hyperbrowser score within a point of each other on agent readiness, 67.7 (B) and 66.9 (B). Hyperbrowser leads on reliability, payments & pricing and transparency & trust.
Do Hyperbrowser and TinyFish need an API key?
Both take 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 Hyperbrowser and TinyFish without installing anything?
Yes. Hyperbrowser has a hosted endpoint at https://api.hyperbrowser.ai and TinyFish at https://agent.tinyfish.ai.
Other comparisons with Hyperbrowser or TinyFish
- agent-browser vs Hyperbrowser
- agent-browser vs TinyFish
- Airtop vs Hyperbrowser
- Airtop vs TinyFish
- Anchor Browser vs Hyperbrowser
- Anchor Browser vs TinyFish
- Browser Use vs Hyperbrowser
- Browser Use vs TinyFish
- Browserless vs Hyperbrowser
- Browserless vs TinyFish
- Chrome DevTools MCP vs Hyperbrowser
- Chrome DevTools MCP vs TinyFish
- Hyperbrowser vs Notte
- Hyperbrowser vs Playwright MCP
- Hyperbrowser vs Puppeteer (archived MCP reference server)
- Hyperbrowser vs Skyvern
- Hyperbrowser vs Steel
- Notte vs TinyFish
- Playwright MCP vs TinyFish
- Puppeteer (archived MCP reference server) vs TinyFish
- Skyvern vs TinyFish
- Steel vs TinyFish
- Browserbase vs Hyperbrowser
- Browserbase vs TinyFish
Machine-readable
- This page as Markdown
/compare/hyperbrowser-vs-tinyfish.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperbrowser.json·/api/v1/tools/tinyfish.json - From a terminal
anchor compare hyperbrowser tinyfish(the CLI) - Over MCP
compare_tools {"a": "hyperbrowser", "b": "tinyfish"}at/mcp, no key