Head to head · Browser automation · October 2026 research run
Notte vs TinyFish
TinyFish scores 67.7 (B) on agent readiness against Notte's 63.2 (B), and leads in 5 of 7 scored categories. Both do browser automation.
Which one, for what
Notte B
Good 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 shows the Scrape API down on 15 of 90 days (about 6 hours in total) and CAPTCHA solving at 88.9 per cent availability
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 74
- Payments & pricing, 55 against 40
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 | Notte | TinyFish | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 58 | 60 | TinyFish +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 74 | 85 | TinyFish +11 |
| Agent ergonomics | 13%16.2 | 75 | 79 | TinyFish +4 |
| Security & auth | 14%17.5 | 56 | 57 | TinyFish +1 |
| Payments & pricing | 10%12.5 | 40 | 55 | TinyFish +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 83 | 80 | Notte +3 |
| Transparency & trust | 7%8.8 | 61 | 59 | Notte +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 63.2 · B | 67.7 · B |
Facts side by side
| Fact | Notte | TinyFish |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Notte Labs Inc. | Tiny Fish, Inc. |
| Hosted endpoint | https://api.notte.cc | https://agent.tinyfish.ai |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service under Notte's terms of service. The core repository is SSPL-1.0 and the Node SDK is MIT | 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 | 8 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | ai.tinyfish.agent/web-agent |
| Last release | 2026-10-07 | 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 | 1.3k npm/wk, 5.1k PyPI/wk | 5.7k npm/wk, 6.5k PyPI/wk |
Verdicts
Notte
Notte publishes an OpenAPI 3.1 contract for 100 operations, a hosted MCP server with eight tools and OAuth, and a free plan with $10 of credits and no card. Its status page records about six hours of Scrape API downtime in 90 days, and a bot check blocked our read of the terms and privacy policy.
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
Notte
- Send
Authorization: Bearer $NOTTE_API_KEYto https://api.notte.cc. A person creates the key in the console at console.notte.cc first - 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
- Use https://api.notte.cc/mcp for browser work. Function and agent administration tools are only on https://api.notte.cc/mcp/full
- Back off on 429 and on 529, which means the cluster has too many sessions. The SDKs do not retry rate limits for you
- Download session replays within 24 hours. The recordings page says they are deleted after that
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, Notte or TinyFish?
TinyFish scores 67.7 (B) on agent readiness against Notte's 63.2 (B), and leads in 5 of 7 scored categories.
Do Notte and TinyFish need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Notte and TinyFish without installing anything?
Yes. Notte has a hosted endpoint at https://api.notte.cc and TinyFish at https://agent.tinyfish.ai.
Other comparisons with Notte or TinyFish
- agent-browser vs Notte
- agent-browser vs TinyFish
- Airtop vs Notte
- Airtop vs TinyFish
- Anchor Browser vs Notte
- Anchor Browser vs TinyFish
- Browser Use vs Notte
- Browser Use vs TinyFish
- Browserless vs Notte
- Browserless vs TinyFish
- Chrome DevTools MCP vs Notte
- Chrome DevTools MCP vs TinyFish
- Hyperbrowser vs Notte
- Hyperbrowser vs TinyFish
- Notte vs Playwright MCP
- Notte vs Puppeteer (archived MCP reference server)
- Notte vs Skyvern
- Notte vs Steel
- Playwright MCP vs TinyFish
- Puppeteer (archived MCP reference server) vs TinyFish
- Skyvern vs TinyFish
- Steel vs TinyFish
- Browserbase vs Notte
- Browserbase vs TinyFish
Machine-readable
- This page as Markdown
/compare/notte-vs-tinyfish.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/notte.json·/api/v1/tools/tinyfish.json - From a terminal
anchor compare notte tinyfish(the CLI) - Over MCP
compare_tools {"a": "notte", "b": "tinyfish"}at/mcp, no key