TinyFish is the one layer I actually keep in the stack when I need live web, not another chatbot pretending it can browse. Search, Fetch, Browser, and Agent sit under one API, so I am not wiring Exa for search, Firecrawl for markdown, and Apify for the messy pages. Yes. For how I actually use TinyFish, I’m getting more than I’m paying.

Search and Fetch are free like 30 searches/min, 150 fetches/min, no Wallet draw even at $0. That’s 90% of my work: live recon, clean page content, Reddit/HN/X/LinkedIn listening, lead-gen. I’m not burning credits on the daily path. Review collected by and hosted on G2.com.

Search + Fetch is the sweet spot. Agent is heavier and I do not want it on every listening sweep. MCP is great in Claude/Cursor; connecting it as a custom connector elsewhere (Perplexity-style OAuth) was fiddly. It is also not Exa if I need semantic “find me papers/pages like this,” I still reach for Exa. TinyFish is live web + browser, not neural retrieval Review collected by and hosted on G2.com.