The agent successfully assembled a comprehensive explanation of My Systems by Axis Communications, but had to work around a fundamentally non-navigable primary domain (mysystems.axis.com is a client-side SPA with no server-rendered content). The agent pivoted to Axis's main marketing site, help documentation, and user manuals to answer the task. The site's architecture made direct discovery impossible; prior knowledge and targeted web search accounted for 88% of source discovery.

• ›The mysystems.axis.com domain itself returned only an empty HTML shell with a single JavaScript bundle ([1–6]); no navigable content about features, pricing, positioning, or differentiators existed server-side. All substantive content required external sources.
• ›Step [9] (www.axis.com/mysystems marketing page) provided positioning, use cases, and feature overview; step [10] (help.axis.com documentation) supplied technical details and user guidance; step [13] (user manual PDF) contained operational specifics. None of these URLs were discovered by following links from mysystems.axis.com—all were sourced via web search or prior knowledge.
• ›Pricing information remained intentionally opaque: the agent could not find concrete pricing anywhere and correctly noted this as a major information gap. The site does not publish AXIS Device Manager Extend pricing; resellers must be contacted. This is an accessibility gap for machine agents (and humans).
• ›The agent had to infer product relationships (My Systems vs. AXIS Device Manager vs. AXIS Device Manager Extend vs. AXIS Camera Station) by synthesizing scattered documentation and search results, rather than finding a clear hierarchy on the site.
• ›The site is **poor for agent discovery**: a client-side SPA with no indexable content, no structured data (schema.org, JSON-LD), and no API documentation. The task succeeded only because Axis maintains separate marketing/documentation domains that are well-indexed and fetchable.