ora
mirantis.com
success
Claude Code
intent

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

7steps
48.4sduration
$0.4237cost
25,662tokens
8 steps1 reasoning step1 search
home
docs
/products
/why-mirantis
search
/k0rdent-ai-pricing
docs
60%
answer from your site
83%
answer efficiency
80%
followed site links
answer sources
  • from this site60%
  • from search results20%
  • from agent knowledge20%
url discovery
  • given in the task17%
  • followed a link67%
  • found via web search17%
insight

The agent successfully gathered a comprehensive overview of Mirantis' business model, target market, and competitive positioning by fetching core site pages (homepage, products, about, why-mirantis). However, the site failed to expose pricing information transparently—the dedicated /pricing URL returned 404, and product pricing pages contained no costs—forcing the agent to rely on third-party review sites and search results to explain that pricing is custom and enterprise-tier.

  • The homepage and core pages (about, products, why-mirantis) provided clear, substantial content about company mission, product stack, customer base, and differentiators—all directly fetched and cited in the final response.
  • Pricing is deliberately hidden behind a sales-gated model: /pricing returns 404, individual product pricing pages (e.g., k0rdent AI pricing) exist but contain no cost information, and the agent had to search external review aggregators (Capterra, TrustRadius, G2, Vendr) to convey that pricing is 'steep' and requires a quote.
  • The agent correctly identified and surfaced this friction point as a notable gap, making the pricing opacity explicit in the final answer rather than pretending information it could not retrieve was unavailable.
  • Product naming and positioning required assembly from multiple pages: the homepage introduced 'k0rdent' as open-source, products page showed Enterprise and AI variants, and about/why pages supplied the 'metal-to-model' positioning and competitive framing—no single page provided the full strategic picture.
  • The agent's final response structure (What/Who/Pricing/Differentiation/Gaps) directly aligned with the task request ('what they do, who it's for, how it's priced, how it's different, confusing bits'), and all substantive claims were sourced to either fetched site pages or explicitly cited third-party sources.

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 →