ora
zerosettle.io
success
Claude Code
intent

What does zerosettle.io do and who is it for? Explain it back to me.

17steps
64.9sduration
$0.1245cost
78,549tokens
22 steps5 reasoning steps3 searches
home
docs
/entitlements
/features
/product
/why
docs
docs
/vs
docs
/merchant-of-record
search
/byos
docs.home
search
search
/autopilot
86%
on-site discovery
36%
reliability
29%
link following
path origin
  • previous resource29%
  • web search14%
  • prior knowledge57%
insight

The agent successfully gathered enough information to explain ZeroSettle's core value proposition, pricing structure, and positioning relative to competitors, though it had to work around a sparse site structure and heavy reliance on prior knowledge and external search results. The homepage and pricing page provided the foundation, supplemented by dedicated feature pages (Autopilot, BYOS) and external comparison articles, but the site lacks a cohesive narrative tying everything together—the agent had to assemble the answer from fragments rather than finding a single, authoritative source.

  • ›Step [1] (homepage) and step [3] (pricing) were the only two pages on zerosettle.io that successfully loaded and contained substantive information. They provided the tagline ('revenue growth engine for apps'), pricing tiers, MoR vs BYOS fee structure, and feature names—but not full explanations of what those features do or how they differ from alternatives.
  • ›Steps [14] (Autopilot) and [16] (BYOS) filled critical gaps the homepage missed: Autopilot's page explained the AI pricing experiment feature; BYOS explained the Bring Your Own Stripe workflow. The agent had to guess these URLs rather than discovering them from navigation—indicating poor information architecture or missing navigation links on the main pages.
  • ›Step [17] (docs.zerosettle.io) was discoverable only via web search, not linked from the main site; it likely contained more detail but the agent did not fetch its content in detail, instead relying on prior knowledge and external comparison articles (steps [19], [20]) to answer the 'alternatives' question. External sources (not from zerosettle.io) provided the competitive positioning that the site itself did not.
  • ›The site structure is brittle for agent navigation: 11 out of 18 fetch attempts returned 404 (steps [4]–[7], [10]–[12], [15]), suggesting either a minimal site footprint or routing issues. The agent succeeded despite this by guessing specific feature URLs and leaning on web search to find docs and comparisons.
  • ›Prior knowledge accounts for 57% of sourcing, web search 14%, and previous artifacts 29%—a heavy bridge. The agent had to synthesize ZeroSettle's positioning (vs RevenueCat, Paddle, Stripe) almost entirely from external articles and prior knowledge, not from ZeroSettle's own site, indicating the site does not publish a competitive comparison or detailed alternatives narrative.

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 →