tinyfish.ai
success
Claude Code
intent

What does tinyfish.ai do and who is it for? Explain it back to me.

11steps
59.4sduration
$0.5298cost
123,351tokens
20 steps9 reasoning steps2 searches
home
docs
/features
docs
docs.home
docs
search
docs
/api
search
docs
78%
on-site discovery
56%
reliability
33%
link following
path origin
  • previous resource33%
  • web search22%
  • prior knowledge44%
insight

The agent successfully assembled a comprehensive explanation of TinyFish's offerings, pricing, and differentiation by combining fetched homepage content, pricing page, about page, and blog articles with web search results. The site surfaced most core information on public pages (homepage, pricing, about), but detailed feature comparisons and API documentation were either inaccessible (404s on /docs, /api, /features) or required guessing URLs, forcing the agent to rely on prior knowledge and search results to fill gaps. The final answer is accurate and complete enough to explain TinyFish to someone else, though several operational details (step definition, rate limits, compliance) remain undocumented on accessible pages.

  • ›Steps [1], [3], [9] returned homepage, pricing, and about pages that contained core value proposition, pricing model (Search/Fetch free; Agent $0.016/step; Browser $0.002/min), and customer names. These were the primary content sources.
  • ›Steps [13] and [18] (blog articles on Browserbase alternatives and API selection) were discoverable only via web search [11] and [16]—the site does not appear to have a blog index or internal navigation to these comparison resources. The agent had to guess they existed.
  • ›Steps [5], [6], [15] show that /features, /docs, and /api paths return 404s, indicating the site has not published detailed technical documentation, feature breakdowns, or API reference in discoverable locations. The agent worked around this by citing external sources (MarkTechPost, blockchain.news, BitDoze).
  • ›The agent relied heavily on prior knowledge (44% of fetches) to construct details about the four APIs (Search, Fetch, Browser, Agent), cold start times (250ms), and token efficiency claims. These were not explicitly cited from fetched content in the final response.
  • ›The site is minimally agent-ready for discovery: core information exists on public pages but is not structured for machine parsing (HTML only, no JSON-LD, no structured comparison tables). Deeper product knowledge required web search rather than traversal of the site itself.

See every agent that visits tinyfish.ai

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →