justsplitbill.com
success
Claude Code
intent
What does justsplitbill.com do and who is it for? Explain it back to me.
6steps
37.4sduration
$0.2083cost
25,896tokens
8 steps2 reasoning steps
home
home
home
home
/privacy
/help
80%
answer from your site
50%
answer efficiency
100%
followed site links
answer sources
- from this site80%
- from agent knowledge20%
url discovery
- given in the task17%
- followed a link83%
insight
The agent successfully built a comprehensive overview of Just Split Bill's core value, pricing, and competitive positioning by assembling facts from the homepage across three fetches. However, the site's help and privacy documentation were inaccessible (404 errors), forcing the agent to flag sustainability and data-handling questions as unresolved gaps.
- ›The homepage (fetches [1]–[3]) was the sole content-bearing source; all facts came from repeated fetches of the same URL, suggesting the site publishes a complete, self-contained pitch without linking to deeper docs or help pages that would have enriched the answer.
- ›Help and Privacy pages both returned 404 errors ([5]–[6]), indicating either dead links or routing issues—documentation the agent would have relied on to answer questions about data persistence, server storage, and long-term viability is unreachable even from the homepage.
- ›The agent synthesized multiple dimensions (business model, settlement algorithm, comparisons to Splitwise/KittySplit/Tricount) from a single homepage response, suggesting the site packs all positioning and differentiators into one text block rather than structuring them across discoverable pages.
- ›No search results were used (0% discovery from web-search); the agent relied entirely on direct URL fetches and inferred links, leaving open whether search engines surface the site well or whether search results would have provided alternative entry points to help or competitor-comparison pages.
- ›The agent explicitly called out unresolved questions (revenue sustainability, data storage, URL/code persistence) with high confidence these were site gaps, not fetching errors—model memory inferred what *should* be documented rather than filling in answers, preserving the distinction between site content and unsupported claims.
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 →