ora
realanalytica.com
success
Claude Code · Haiku 4.51:42
intent

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

24steps
102.6sduration
$1.9647cost
363,856tokens
38 steps14 reasoning steps14 searches
home
docs
/agents
docs
/features
docs
search
/p/10039170/realanalyt…
search
search
search
search
search
search
/faqs
search
/compare
/alternatives
search
search
search
search
search
search
60%
on-site discovery
80%
reliability
30%
link following
path origin
  • previous resource30%
  • web search40%
  • prior knowledge30%
insight

The agent successfully assembled a comprehensive explanation of RealAnalytica's business model, pricing, target market, and differentiation, but had to work around a heavily client-side-rendered website that exposed minimal content via standard fetches. The site's own pages (homepage, pricing, features, about, FAQ) returned only HTML shells without readable text, forcing the agent to rely on 40% web search results and 30% prior knowledge to construct the final answer. The agent identified critical gaps (geographic limitations, security concerns, feature parity uncertainty) that the site itself does not prominently surface.

  • All direct fetches of RealAnalytica's own pages ([1], [3], [5], [7], [8], [36]) returned truncated, client-side-rendered HTML stubs with preloaded fonts but no readable content; the agent could not extract product details, pricing tiers, or feature lists from the site's own infrastructure.
  • The agent relied on web search results ([10], [11], [16], [17], [19], [20], [22], [27], [28], [30]) to reconstruct what should have been on the site — search engine snippets and indexed pages contained more readable information about Atlas Agents, pricing ($40/month, $20/month team rates), and feature names (Ivy, Alex, Lucia, Scout, Ren, Miles) than the site's HTML responses.
  • The agent discovered comparison and alternatives pages (vs. BoomTown, kvCORE, MoxiWorks, Zillow) only via search results and URL inference, not via navigation or site architecture; these pages exist but their content was not accessible via direct fetch.
  • Critical limitations the agent flagged (Northeast-only MLS coverage, security audit concerns, lack of IDX website builder, pricing ambiguity) were NOT found on the site itself — they emerged only from third-party sources and search engine results, indicating the site obscures or does not disclose drawbacks.
  • The pricing page ([3]) returned no readable content despite being a task-critical resource; the agent had to infer pricing from search snippets rather than official documentation.
  • The agent explicitly cited sources from RealAnalytica's own domain (pricing page, Atlas Agents page, team/brokerage solutions pages, comparison pages, FAQ) in its final answer, but none of these actually returned machine-readable content during the run — the citations reflect URLs inferred from search results and prior knowledge, not direct content validation.

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 →