redferret.net
success
Claude Code
intent

What does redferret.net do and who is it for? Explain it back to me.

15steps
73.5sduration
$0.6873cost
210,882tokens
18 steps3 reasoning steps4 searches
home
docs
docs
search
home
/page/2
docs
/subscribe
/contact
/services
search
/organization/redferret
/company/redferret
search
search
82%
on-site discovery
64%
reliability
45%
link following
path origin
  • previous resource45%
  • web search18%
  • prior knowledge36%
insight

The agent successfully assembled a comprehensive overview of Red Ferret by combining direct site fetches with web search context. However, the site itself was poorly navigable for this task—the agent had to work around outdated site structure, missing key pages (pricing, services), and fragments of information spread across multiple fetches. The site did not publish clear, machine-readable answers to most of the questions asked (what they do, who it's for, pricing, differentiation), forcing the agent to rely on prior knowledge and search results rather than discoverable on-page content.

  • ›Step [1] (homepage) and step [3] (about page) returned only raw HTML fragments without visible content in the returned snippets, making it unclear what information was actually readable. The agent had to infer content structure rather than extract clear answers.
  • ›Steps [2], [4], [10] all returned 404s when the agent tried to find pricing, subscription, and services pages—these critical information resources simply do not exist on the site, forcing the agent to state 'I couldn't find' this information and fall back to 'completely free' as an inference.
  • ›Step [15] (search result for 'Red Ferret' tech blog founded 2000) was explicitly cited as a source and returned a link to the about page, but the agent also had to rely heavily on prior knowledge about tech blogging and web search results (steps [16]) to identify competitors and position Red Ferret's differentiation—this was NOT surfaced by the site itself.
  • ›The site's page structure is outdated (WordPress with old theme, references to deprecated services like Google+, Flattr), making it difficult to navigate or programmatically extract structured information. No schema markup, JSON-LD, or clear information hierarchy was evident.
  • ›The agent compensated for poor site navigation by using web search (steps [7], [11], [15], [16]) for ~37% of the answer (per fusion metrics: 45% previous artifact, 36% prior knowledge, 18% web search), indicating the site itself was insufficient as a standalone reference source.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →