axiusflow.com
success
Claude Code
intent
What does axiusflow.com do and who is it for? Explain it back to me.
15steps
63.9sduration
$0.8732cost
159,337tokens
19 steps4 reasoning steps6 searches
home
docs
/story
/features
search
/why-axiusflow
docs
docs
/demo
search
search
search
search
search
home
100%
on-site discovery
44%
reliability
33%
link following
path origin
- previous resource33%
- prior knowledge67%
insight
The agent successfully gathered enough information to explain Axiusflow's core value proposition, target audience, pricing, and differentiation, though it worked around a sparse website with many 404s and limited public documentation. The site surfaces only a homepage, pricing page, and story page; the agent had to rely heavily on prior knowledge (67% of fetches) and web search to fill gaps, since the site itself does not publish detailed feature lists, comparisons, team info, or launch status in accessible pages.
- ›Step [1] (homepage) returned the core pitch and founder name, but as heavily obfuscated Next.js HTML with minimal semantic markup — the agent had to decode the content from truncated, rendered DOM rather than clean text or structured data.
- ›Step [2] (pricing page) was the only secondary page that returned a 200; it contained the three-tier pricing model ($0, $29, $59, $1,499) explicitly cited in the final response, making it a critical content source.
- ›Step [3] (/story page) was accessible but its content is not shown in detail in the trajectory, yet the agent cited it as a source — indicating it contained founder/context narrative that reinforced the 'solo founder project' observation.
- ›Steps [4, 7, 8, 9, 10] all returned 404s, indicating the site has minimal navigation structure; the agent had to guess at standard URL patterns (/features, /about, /why-axiusflow, /blog, /demo), none of which exist.
- ›The agent filled knowledge gaps using prior knowledge (67%) rather than site content — claims about Rust architecture, AI trade review, Origin Charts, WebAssembly performance, and competitor positioning came from the knowledge base, not from fetched content, because the site does not publish a features or positioning page.
- ›Web searches [6, 11, 12, 13, 14, 15] returned only the homepage URL repeatedly, indicating the site has minimal SEO or external coverage; they did not yield independent verification of features or comparisons.
- ›The final response's 'Sources' section cites only the three fetched pages (homepage, pricing, story), even though the agent relied on prior knowledge for 67% of factual claims — a sign the site is not self-documenting and the agent had to bridge gaps synthetically.
Help the next agent finish on axiusflow.com
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 →