vexo.co
success
Claude Code
intent

What does vexo.co do and who is it for? Explain it back to me.

15steps
58.3sduration
$0.7938cost
156,568tokens
19 steps4 reasoning steps5 searches
home
docs
/features
docs
search
docs
search
/products/vexo/competi…
/products/vexo/alterna…
search
/heatmaps
search
/products/vexo/reviews
search
docs.home
40%
on-site discovery
70%
reliability
10%
link following
path origin
  • previous resource10%
  • web search60%
  • prior knowledge30%
insight

The agent successfully gathered enough information to explain Vexo's core offering, target audience, pricing tiers, and competitive differentiation, though it had to work around fragmented pricing information and missing detailed comparison resources. The website published feature descriptions and basic pricing across multiple pages and documentation, but lacked a unified pricing page, and several third-party comparison sites were blocked. The agent synthesized information from the homepage, feature pages, documentation, and web search results to build a coherent explanation.

  • ›Steps [1], [4], [5], [17] retrieved feature-specific landing pages (session replays, heatmaps, features) that the agent used to define Vexo's capabilities—these were directly discoverable from the site structure and cited in final sources.
  • ›Steps [3] (pricing route) and [10] (subscription docs) contained pricing tiers and plan details, but pricing was scattered: the /pricing path returned content, yet the agent notes 'No Detailed Pricing Page' and describes pricing as 'scattered across documentation and product pages'—the site forced reconstruction rather than presenting pricing as a unified resource.
  • ›Step [9] (docs.vexo.co root) was a redirect-only fetch that did not contribute content; it was not cited. Step [16] was a search that returned link snippets but no pricing or competitor data directly in snippets—the agent relied on prior knowledge and subsequent fetches.
  • ›Blocked resources (steps [13], [14], [15]—G2, Product Hunt alternatives) prevented direct competitor comparison; the agent worked around this by citing 'Main competitors mentioned in comparisons' without evidence from those sites, relying instead on prior knowledge and general market knowledge.
  • ›The agent correctly identified missing information gaps (data residency, web feature parity, team collaboration details, enterprise scaling model) and flagged the lack of a unified pricing page—indicating the site is not optimized for agent-ready pricing disclosure.

See every agent that visits vexo.co

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 →