truesite.ai
success
Claude Code
intent

What does truesite.ai do and who is it for? Explain it back to me.

15steps
66.8sduration
$1.0392cost
221,798tokens
23 steps8 reasoning steps6 searches
home
docs
/features
docs
search
/platform
home
search
/features
search
search
search
docs
docs
search
67%
on-site discovery
100%
reliability
56%
link following
path origin
  • previous resource56%
  • web search33%
  • prior knowledge11%
insight

The agent successfully gathered enough information to explain what TrueTone AI does, who it serves, how it's priced, and how it differs from competitors, though the website's HTML responses were truncated and largely unreadable, forcing heavy reliance on search results and prior knowledge to construct the answer. The site proved difficult to navigate programmatically—all direct fetches returned truncated HTML—but the agent worked around this by using web search to confirm URLs and by synthesizing information from multiple source mentions across search results.

  • ›All direct fetches of truesite.ai pages ([1], [3], [4], [5], [13], [14], [19]) returned truncated HTML with no usable content; the agent could not extract information from the actual site pages despite successfully reaching them (HTTP 200).
  • ›The agent's final answer was constructed primarily from web search results ([7], [11], [12], [16], [17], [21]) that mentioned TrueTone AI's positioning, features, and pricing, not from the site's own rendered content. Search result titles and meta-descriptions proved more informative than the fetched pages themselves.
  • ›The agent correctly identified key information (pricing at $199/month or $1,990/year, target audience as mortgage professionals, voice profile as core differentiator) but had to acknowledge multiple information gaps (what 'AI credits' are, integration specifics, team workflows) because the site content was inaccessible.
  • ›The agent's citations reference URLs that were discovered via search or direct guessing, not because the site's navigation structure made them discoverable—this indicates the site lacks clear internal linking or was not rendering its content to the crawler.
  • ›Pricing page [19] was confirmed to exist but returned no readable content; the agent's pricing details likely came from search result snippets rather than from the actual pricing page fetch.

See every agent that visits truesite.ai

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 →