ora
mathworks.com
success
Claude Code
intent

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

12steps
49.3sduration
$0.5174cost
114,791tokens
14 steps2 reasoning steps2 searches
home
/products.html
docs
/about.html
/store
/products/matlab.html
/products/simulink.html
search
/pricing-licensing.html
search
/licensecenter.html
/help/matlab/getting_s…
90%
on-site discovery
60%
reliability
40%
link following
path origin
  • previous resource40%
  • web search10%
  • prior knowledge50%
insight

The agent successfully assembled a comprehensive explanation of MathWorks by combining direct site navigation (homepage, products pages, store) with a web search to locate the pricing page. The site's information architecture forced the agent to use prior knowledge and web search to find pricing details, as the standard /pricing and /about URL patterns returned 404s. The agent delivered a well-rounded answer covering what MathWorks does, target users, pricing tiers, and competitive positioning, though some information required external research rather than site-native discovery.

  • Steps [1], [2], [5], [6] returned product descriptions and positioning (MATLAB, Simulink, 90+ toolboxes) that directly grounded the 'what they do' and 'who it's for' sections of the final answer.
  • The pricing information (step [10], sourced via web search in step [7]) was the only place on-site that clearly structured licensing tiers and subscription costs; the standard /pricing URL did not exist, forcing indirect discovery.
  • Steps [5] and [6] exposed meta descriptions and content positioning but not detailed pricing or competitive comparison—the agent had to rely on external search results (step [11]) to contextualize alternatives (Python, R, Octave, Mathematica).
  • The site's navigation pattern is fragile: /pricing, /about, /licensecenter all returned 404s, suggesting URL structure is non-standard or recently changed. The agent recovered by guessing /pricing-licensing.html after a web search revealed it.
  • Store page (step [9]) loaded successfully but the response was truncated in the log, so actual buyflow or trial information visibility is unclear from this trajectory.
  • Pricing-licensing page (step [10]) was cited directly in the final response's source list, confirming it was content-bearing for the pricing section of the answer.
  • The agent did not fetch detailed toolbox pricing, trial terms, or cloud offerings—these gaps were acknowledged in the final response as 'confusing or missing information,' indicating the site does not expose these details prominently on traversable pages.

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 →