clario.com
success
Claude Code
intent

What does clario.com do and who is it for? Explain it back to me.

17steps
91.6sduration
$0.9822cost
205,500tokens
26 steps9 reasoning steps6 searches
home
docs
docs
/features
search
/solutions/cardiac-sol…
search
/solutions/medical-ima…
search
docs
/wp-json/wp/v2/article…
search
search
/solutions
/platform
/wp-json/wp/v2/pages/8
search
73%
on-site discovery
73%
reliability
64%
link following
path origin
  • previous resource64%
  • web search27%
  • prior knowledge9%
insight

The agent successfully assembled a comprehensive overview of Clario by combining fragments from the site's JSON API, blog articles, and third-party sources, since Clario's main pages are JavaScript-heavy and content-sparse. The site proved poorly navigable for machine extraction—pricing information was entirely absent, core product pages returned 404s, and most useful details came from external comparisons rather than Clario's own published content. The agent had to rely heavily on prior knowledge and web search (91% of fetches) to fulfill the task.

  • ›Step [15] (homepage JSON API) and [21] (eCOA article JSON) returned structured content about services and clinical outcomes, but only in isolated, topic-specific chunks—no unified product overview was published on the site itself.
  • ›Clario's main navigation failed: /pricing, /features, and /platform all returned 404s, forcing the agent to infer the product model from solution subpages (/solutions/cardiac-solutions, /solutions/medical-imaging) and third-party comparison articles. The site's architecture doesn't surface its own positioning.
  • ›Pricing—a core part of the task—was completely inaccessible on clario.com. The agent found a single oblique reference ('less than $100,000' for CTMS) via prior knowledge, then had to explain this absence to the user. No public pricing page exists.
  • ›Steps [16], [22], [24] were web search results (not direct site fetches) that provided the most actionable competitive differentiation, customer profile, and business context—suggesting Clario's own website does not adequately answer discovery-evaluation questions.
  • ›The site's heavy JavaScript rendering (noted in every HTML response) and Nitro CDN setup make static scraping difficult; the agent resorted to the WordPress JSON API (/wp-json/) endpoints as a workaround, which is not a documented public interface.
  • ›The agent explicitly cited third-party sources (G2, RFP.wiki, IntuitionLabs, Castor, Wikipedia, and news articles) in the final answer because Clario's own site did not provide competitive or business model clarity—a major gap for an 'understand the product' task.

Help the next agent finish on clario.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 →