The agent successfully assembled a comprehensive overview of Onyx Security by combining content from the company's own site (homepage, platform, and blog pages) with third-party reviews and news coverage. The official site provided core positioning and feature details, but lacked pricing, technical depth, and competitive comparisons—forcing the agent to rely on external sources and prior knowledge to fill critical gaps. The site is minimally navigable for self-service discovery; most subpages returned 404s, and the agent had to guess URLs or use search.

• ›Step [1] (homepage) and step [18] (platform page) established what Onyx does—a control plane with five core components (observability, security, governance, orchestration, ROI measurement)—and introduced the proprietary Guardian Agent. Step [19] (blog post) reinforced positioning and stealth launch context. These three steps were the primary on-site sources of product definition.
• ›Steps [11] and [12] (third-party reviews and comparison sites) provided competitor positioning, funding details ($113M Series B, $640M valuation), and concrete differentiation claims that were absent from Onyx's own site. The agent had to leave the domain to answer 'how it's different from alternatives.'
• ›Pricing was entirely absent from the official site; step [3] (pricing URL) and step [8] (solutions URL) returned 404s. Steps [4] and [9] (features, how-it-works) also returned 404s. The agent disclosed this gap transparently in the final response, indicating the site lacks standard product information architecture.
• ›The homepage and platform page were fetched via prior knowledge / direct guess (steps [1], [18]), not discovered through internal navigation. No visible sitemap or structured discovery mechanism was present. Web search (steps [7], [13], [15], [16]) became the primary discovery method for secondary content.
• ›The agent relied on web search results and external sources for 40% of sourcing and prior knowledge for 20%, indicating the official site alone was insufficient to fulfill the task. The site is agent-unfriendly for open-ended evaluation: minimal information hierarchy, no pricing, no competitive positioning, and broken internal navigation.
• ›Step [5] (About page) provided company context (70 employees, offices in Israel/US/Canada, Fortune 500 deployments) that grounded the 'who it's for' answer, but this required a separate fetch and was not woven into the homepage narrative.