bri.so
success
Claude Code
intent
What does bri.so do and who is it for? Explain it back to me.
13steps
86.6sduration
$0.1055cost
71,964tokens
14 steps1 reasoning step2 searches
home
home
docs
home
/compare
home
search
search
/ai-podcast
docs
/faq
home
docs
60%
answer from your site
45%
answer efficiency
70%
followed site links
answer sources
- from this site60%
- from agent knowledge40%
url discovery
- given in the task9%
- followed a link64%
- found via web search18%
- guessed the URL9%
insight
The agent assembled a usable overview of Bri's core offering (RSS-to-podcast conversion, target audience, competitive positioning) from the site's homepage and comparison page, but the site's complete absence of accessible pricing information forced the agent to acknowledge a critical gap rather than fill it with guesses. Navigation was straightforward for product discovery but deliberately opaque for commercial terms.
- ›The site successfully surfaced product positioning and feature descriptions on the homepage and /compare page, providing clear answers to 'what it does' and 'who it's for,' but made zero pricing information publicly accessible across all attempted fetch paths (/pricing returned 404, FAQ questions listed but answers not rendered, homepage mentioned free tier question without answering it).
- ›The comparison page ([4]) was the richest source for differentiation claims, explicitly positioning Bri against Feedly, NotebookLM, Zapier/IFTTT, and general agents — this information was site-sourced and well-structured, eliminating need for external research on positioning.
- ›Pricing information proved completely unavailable: web search results ([6], [7]) returned unrelated products (Bria AI, Brevo, RSS.com) and did not locate Bri.so pricing in public search indexes, indicating the site either does not publish pricing publicly or does so only behind authentication.
- ›The agent correctly identified and cited four on-domain sources in its final response, all of which successfully fetched and contributed content (homepage, /ai-podcast, /compare, /docs), demonstrating that the site's public URL structure is navigable and its key pages are fetchable.
- ›The agent's 'What Was Confusing' section accurately reflects a genuine site gap rather than agent failure: the FAQ lists a free-tier question as if answering it, but the answer never renders in the fetched content, and no alternative pricing disclosure mechanism exists.
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 →