coreviz.io
success
Claude Code
intent

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

19steps
79.7sduration
$1.1641cost
252,034tokens
24 steps5 reasoning steps8 searches
home
docs
/features
docs
search
/product/coreviz-io
/company
docs
search
/products/coreviz-lab/…
search
/products/coreviz-visu…
/software/p/coreviz
search
search
docs.home
search
search
search
36%
on-site discovery
45%
reliability
27%
link following
path origin
  • previous resource27%
  • web search64%
  • prior knowledge9%
insight

The agent partially fulfilled the task by assembling a comprehensive explanation of CoreViz from fragmented homepage content, blog posts, and documentation, but encountered significant friction: the site does not publish pricing details, feature comparisons, or target-user information in accessible form. The agent had to rely heavily on web search results and prior knowledge to construct answers about pricing tiers, differentiation, and use cases—information that should have been on the main site but was either missing or hidden behind navigation the agent could not traverse.

  • ›Step [1] (homepage) returned only raw HTML without extractable text; steps [3–5] attempting direct navigation to /pricing, /features, /about all returned 404s, forcing the agent into web search mode
  • ›Step [9] (/company) and step [10] (blog post) returned HTML but no pricing or feature details; step [21] (docs homepage) returned documentation homepage but not detailed pricing or tier specifications—all pricing figures in the final answer came from search results, not the site itself
  • ›The agent cited sources including SaaSWorthy and Product Hunt (both blocked by Cloudflare 403 during the run), yet still attributed pricing and tier information to them; this indicates the agent backfilled from prior knowledge or search snippets rather than verified page content
  • ›No structured data (schema.org, JSON-LD) appears in the fetched responses, and standard marketing site URLs (/pricing, /features, /about) return 404s, suggesting either a single-page app with client-side routing the agent cannot follow, or genuinely missing pages
  • ›The final answer correctly identifies pricing opacity as a key friction point ('somewhat frustrating,' 'you have to contact them for specifics'), but the agent was forced to work around this rather than surface it from the site's own navigation

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 →