SignalStack
Back to feed

TinyFish Makes Search Free: What It Really Costs an AI Agent to Read the Web

Read original

AI summary

TinyFish highlights that AI agents face hidden costs from processing retrieved web content, urging developers to budget for token consumption beyond just API fees.

AI-generated summary. Check the original reporting for context and accuracy.

Source excerpt

This is the available feed excerpt, which may be shortened or in the publisher’s original language.

An AI agent that reads the web pays 2 kinds of cost. The first is the retrieval charge: what a search or fetch API bills per request. The second is model processing: content passed from retrieved pages into an AI model consumes tokens, while reasoning and generated responses add further costs. TinyFish, a web infrastructure company for AI agents, argues that teams budget for the model and underestimate how much retrieved content drives it. This article walks through the token math, the context-window impact, and what the Artificial Analysis Search API leaderboard does and does not show. TL;DR What it runs on: TinyFish uses a web-native AI model designed for search, retrieval, and interaction with live websites. The model runs on TinyFish-managed infrastructure, while its cloud browser fleet renders pages and handles website interactions. No local GPU is needed. Access is via REST, Python and TypeScript SDKs, CLI or MCP. Performance: On the Sep 28, 2026 Artificial Analysis snapshot, TinyFish Search (web) scores 71 at $9.30 per 1,000 benchmark tasks, with 59.0 seconds per task (model plus search time). Best: $0 retrieval charge within rate limits (Search: 30 requests/min, 500/hour; Fetch: 150 URLs/min, 1,000/day), and the lowest total cost among the 12 configurations displayed on the leaderboard. Trade-offs: The second longest time per task among displayed configurations, and an Agent product whose built-in model cannot be swapped. Scores: Highest displayed is Perplexity Search (medium) at 80. Lowest displayed is TinyFish Search (web) at 71. The no-search baseline is 33. Retrieval charges vs model processing costs Search and fetch APIs usually bill per request or per page. Whatever they return then enters the model’s context and is billed as input tokens. Reasoning and output tokens come on top. Enterprises now route each task to the cheapest capable model, a trend underlined when Stripe agreed to acquire OpenRouter, a gateway spanning 400+ models from 80+ p

About priority

An automated sorting aid based on source trust, keywords, and entities, on a scale of 1–12. High: 9–12; medium: 6–8; low: 1–5. It does not measure urgency, verify reporting, or indicate editorial endorsement.

More in this topic