Head to head · Browser automation · October 2026 research run
Browser Use vs TinyFish
Browser Use scores 77.9 (BB) on agent readiness against TinyFish's 67.7 (B), and leads in 4 of 7 scored categories. Both do browser automation. Browser Use accepts x402. TinyFish doesn't.
Which one, for what
Browser Use BB
Good for An agent that wants to hand a whole browser task to a hosted agent and get a result back, or that needs a low-cost cloud browser over CDP, and for unattended agents that can pay by x402.
Ahead on
- Reliability, 87 against 60
- Payments & pricing, 90 against 55
- Transparency & trust, 65 against 59
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
The privacy policy says inputs are used to train Browser Use's AI models, with no opt-out described outside Enterprise zero data retention
TinyFish B
Good for Agents that want one account for a goal-driven web agent, a raw CDP browser, and free search and fetch.
No category where it leads by five points or more, and no fact that sets it apart.
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 | Browser Use | TinyFish | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 87 | 60 | Browser Use +27 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 85 | even |
| Agent ergonomics | 13%16.2 | 78 | 79 | TinyFish +1 |
| Security & auth | 14%17.5 | 59 | 57 | Browser Use +2 |
| Payments & pricing | 10%12.5 | 90 | 55 | Browser Use +35 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 77 | 80 | TinyFish +3 |
| Transparency & trust | 7%8.8 | 65 | 59 | Browser Use +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 77.9 · BB | 67.7 · B |
Facts side by side
| Fact | Browser Use | TinyFish |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Browser Use | Tiny Fish, Inc. |
| Hosted endpoint | https://api.browser-use.com/api/v4 | https://agent.tinyfish.ai |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | yes | no |
| Licence | MIT for the open-source library and the SDK. Browser Use Cloud is a proprietary service under Browser Use's terms of service | 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 |
| Tools exposed | 7 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.browser-use/browser-use | ai.tinyfish.agent/web-agent |
| Last release | 2026-10-07 | 2026-10-07 |
| Terms last updated | 2026-07-15 | 2026-08-17 |
| Privacy policy last updated | no date given | 2025-12-14 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 117k stars, 107k npm/wk, 2.1M PyPI/wk | 5.7k npm/wk, 6.5k PyPI/wk |
Verdicts
Browser Use
The hosted cloud accepts x402 top-ups in USDC on Base with no account or API key, and publishes prices, rate limits and three OpenAPI documents. The privacy policy says inputs are used to train Browser Use's models, API keys have no documented scopes, and no prompt-injection guidance was found in the docs.
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
Browser Use
- Send the key as
X-Browser-Use-API-Keywith no Bearer prefix. A Bearer header returns 401 - Stop browsers with
PATCH /api/v4/browsers/{id}and{"action":"stop"}. Closing CDP or the SDK client leaves the browser billing - Poll
GET /runs/{id}/status, not the full run, and wait for the returned Retry-After on 429, which can be 300 seconds at the edge - Before resubmitting after a timeout, read the existing run's status. The server keeps running and may already have submitted a form
- With a wallet and no key, call x402.api.browser-use.com on
/api/v2or/api/v3routes. A task stops with INSUFFICIENT_CREDITS if credit runs out mid-run
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, Browser Use or TinyFish?
Browser Use scores 77.9 (BB) on agent readiness against TinyFish's 67.7 (B), and leads in 4 of 7 scored categories.
Do Browser Use and TinyFish need an API key?
Browser Use needs an API key. TinyFish takes an API key or an OAuth sign-in. An agent can also pay Browser Use per call over x402, with no account.
Can an agent call Browser Use and TinyFish without installing anything?
Yes. Browser Use has a hosted endpoint at https://api.browser-use.com/api/v4 and TinyFish at https://agent.tinyfish.ai.
Are Browser Use and TinyFish open source?
Browser Use is open source (MIT for the open-source library and the SDK. Browser Use Cloud is a proprietary service under Browser Use's terms of service). No open-source release is listed for TinyFish.
Other comparisons with Browser Use or TinyFish
- agent-browser vs Browser Use
- agent-browser vs TinyFish
- Airtop vs Browser Use
- Airtop vs TinyFish
- Anchor Browser vs Browser Use
- Anchor Browser vs TinyFish
- Browser Use vs Browserbase
- Browser Use vs Browserless
- Browser Use vs Chrome DevTools MCP
- Browser Use vs Hyperbrowser
- Browser Use vs Notte
- Browser Use vs Playwright MCP
- Browser Use vs Puppeteer (archived MCP reference server)
- Browser Use vs Skyvern
- Browser Use vs Steel
- Browserless vs TinyFish
- Chrome DevTools MCP vs TinyFish
- Hyperbrowser vs TinyFish
- Notte vs TinyFish
- Playwright MCP vs TinyFish
- Puppeteer (archived MCP reference server) vs TinyFish
- Skyvern vs TinyFish
- Steel vs TinyFish
- Browserbase vs TinyFish
Machine-readable
- This page as Markdown
/compare/browser-use-vs-tinyfish.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/browser-use.json·/api/v1/tools/tinyfish.json - From a terminal
anchor compare browser-use tinyfish(the CLI) - Over MCP
compare_tools {"a": "browser-use", "b": "tinyfish"}at/mcp, no key