mintlify.com
success
Claude Code
intent
What does mintlify.com do and who is it for? Explain it back to me.
13steps
45.7sduration
$0.0694cost
147,011tokens
16 steps3 reasoning steps
home
/index.md
/product
docs
docs
.well-known
/features
docs
/customers.md
/enterprise.md
/startups.md
/build-vs-buy.md
/data.md
100%
on-site discovery
77%
reliability
31%
link following
path origin
- previous resource31%
- prior knowledge69%
insight
The agent successfully assembled a comprehensive explanation of Mintlify's business model, pricing, target audience, and competitive positioning by fetching eight content-bearing pages (.md files and homepage HTML). The site publishes its core value proposition and pricing through machine-readable markdown endpoints, making discovery straightforward. However, the agent had to rely heavily on prior knowledge (69%) to fill gaps around competitor comparisons and implementation details that weren't explicitly stated on the marketing pages.
- ›Steps [3], [4], [9], [10], [11], [12], [14] returned markdown files (.md endpoints) that contained the actual substance—product positioning, pricing tiers with costs, customer stories, startup programs, and build-vs-buy narrative. These were directly cited in the agent's sources.
- ›The site publishes pricing and positioning as structured .md files at predictable URLs (mintlify.com/pricing.md, /enterprise.md, /startups.md), which enabled the agent to discover them via prior knowledge rather than needing to parse HTML or follow visible navigation links.
- ›Key gaps existed: exact overage pricing details, enterprise pricing (intentionally vague), self-hosting setup complexity, and how the 'self-updating' automation is actually configured. The agent had to acknowledge these unknowns rather than invent answers, indicating the marketing site prioritizes high-level messaging over implementation minutiae.
- ›The agent inferred competitive differentiation (vs. ReadMe, in-house building) from customer testimonials and the 'build-vs-buy' page [12] rather than from explicit feature comparisons, suggesting the site relies on narrative positioning over direct competitor matrices.
- ›Steps [5], [6], [7] returned 404s for /features, /product, /about—conventional navigation endpoints that don't exist. The agent adapted by guessing .md endpoints instead, which worked, showing the site's URL structure is predictable but not conventionally organized for human discovery.
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 →