mozn.sa
success
Claude Code
intent

What does mozn.sa do and who is it for? Explain it back to me.

14steps
58.8sduration
$0.7482cost
140,750tokens
21 steps7 reasoning steps4 searches
home
home
docs
/products
docs
search
/financial-crime-preve…
/enterprise-knowledge-…
search
search
/focal
search
docs
/solutions
90%
on-site discovery
50%
reliability
70%
link following
path origin
  • previous resource70%
  • web search10%
  • prior knowledge20%
insight

The agent assembled a comprehensive overview of MOZN's business by combining the homepage, About page, FOCAL product page, and third-party sources discovered via web search. The site's navigation is minimal and does not expose pricing, detailed product comparison, or a clear product roadmap; the agent had to rely on external sources (press releases, analyst reports, fintech news) to construct a complete picture. Task was satisfied — the agent delivered a usable explanation of what MOZN does, who it serves, and how it differs — but with explicit gaps flagged around pricing opacity and vague secondary offerings.

  • ›The homepage ([1], [2]) and About page ([6]) provided only high-level positioning ('intelligence not chance') without concrete product details; the agent had to reach the FOCAL page ([18]) to learn their flagship offering is an AML/fraud detection platform.
  • ›Pricing was not available anywhere on mozn.ai itself; the agent correctly identified this as a gap and noted enterprise custom-pricing is standard, but the site offers no starting point or tier guidance.
  • ›The 'Enterprise Knowledge Intelligence' offering mentioned in the response was inferred from second-hand sources (press releases, news articles from steps [15], [16], [19]) rather than dedicated product pages on the site itself — /solutions and /products routes returned 404s.
  • ›Web search ([10], [15], [16], [19]) was essential to overcome the site's sparse information architecture; the agent discovered FOCAL details, competitive positioning, analyst rankings, and the HUMAIN investment via external sources, not direct site navigation.
  • ›The site is optimized for brand/positioning messaging (tagline, clean design) but lacks agent-ready artifact pages: no /pricing, /features, /use-cases, or /competitors pages; no structured data (schema.org, JSON-LD) visible in fetches to support programmatic understanding.
  • ›The agent was forced into a 'heavy bridge' pattern, relying on prior knowledge (~20%) and web search (~10%) to fill the 70% gap left by the site's sparse published information.

See every agent that visits mozn.sa

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 →