The agent successfully gathered enough information to explain ankya.ai's core purpose, target audience, and differentiation, but encountered a critical gap: pricing information is not publicly disclosed on the site. The agent assembled its answer primarily from the homepage and service pages (which are client-side rendered and required prior knowledge to locate), supplemented by the sitemap to discover secondary pages. The site's architecture made it difficult to extract complete information automatically.

• ›The homepage [1] and /services page [7] were foundational but heavily client-side rendered (Next.js), making it unclear whether all content was fully extracted. The agent relied on prior knowledge to guess both the homepage URL and the /services path.
• ›Specific service pages [14, 15, 16] (security, cloud, research tools) were discovered via the sitemap [13], not from navigation links, indicating the site's internal linking may not be crawlable without prior site knowledge.
• ›Pricing is deliberately absent from the public site—the agent correctly identified this as 'contact for custom quote' based on site messaging ('No sales cycles') rather than finding an actual pricing page, since /pricing returned 404.
• ›The agent could not extract full service descriptions from the client-rendered pages; it had to rely on inferences from page titles and route structure (e.g., /services/security, /services/cloud) combined with prior knowledge of what ankya does.
• ›No case studies, testimonials, or blog content are available (blog returned 404), limiting the agent's ability to find concrete evidence of their work or thought leadership beyond the LLM ATT&CK Navigator research tool.