ex.co
success
Claude Code
intent
What does ex.co do and who is it for? Explain it back to me.
21steps
68.4sduration
$1.1243cost
265,464tokens
26 steps5 reasoning steps7 searches
home
docs
search
/ad-server
/ovp
search
/pricing-plans
/product/ex-co
/p/10002465/ex-co
search
/pr/ex.co-unveils-larg…
llms.txt
search
search
search
search
/products/ex-co/compet…
docs
home
docs
/product
43%
on-site discovery
64%
reliability
14%
link following
path origin
- previous resource14%
- web search57%
- prior knowledge29%
insight
The agent successfully gathered enough information to explain ex.co's core business, target audience, and differentiation, though pricing details remained opaque by design. The site proved difficult to navigate directly (heavily minified, no public pricing page), so the agent relied on a press release blog post and an LLM-specific info document (llms.txt) to construct its answer. The agent assembled a coherent explanation from fragments rather than finding a single comprehensive source.
- ›Step [22] (ex.co/llms.txt) was the single most valuable resource—a structured, machine-readable document explicitly intended for LLMs that directly answered 'what do they do,' 'who it's for,' and core differentiators. This page was cited and heavily sourced the final answer.
- ›Step [21] (blog press release about LLM-based video recommendation engine) provided concrete product features and performance claims (49% engagement lift, 17% yield lift) that supported the differentiation narrative.
- ›Step [19] (web search) surfaced the llms.txt URL and press release—the agent did not discover these via site navigation but via search. The homepage and about pages returned heavily minified JavaScript with no readable content.
- ›The site deliberately hides pricing (no numbers on pricing-plans page, enterprise negotiation model), making cost comparison impossible—this is intentional but limits agent utility for price-sensitive evaluation.
- ›The agent had to assemble the answer from press releases, an LLM-specific info document, and web search snippets rather than from a cohesive public website. Site structure and navigation are not agent-ready; direct fetches of main pages (/, /about, /ovp, /pricing-plans) all returned unreadable minified code.
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 →