The agent assembled a comprehensive explanation of WSO2 by working around the site's Cloudflare protection (which blocked direct access to wso2.com) and instead synthesized information from third-party sources and search results. The task was satisfied: the agent delivered clear answers to what WSO2 does, who it's for, how it's priced, and how it differs from alternatives—but had to rely entirely on external sources rather than WSO2's own website, revealing poor agent-navigability of the primary domain.

• ›The agent's answer was built from TechTarget definition (step [9]), Yenlo blog (step [10]), Wikipedia (step [11]), and search result snippets (steps [13], [14]). None came directly from wso2.com—the official site was inaccessible due to Cloudflare challenges on all attempted URLs (steps [1], [2], [3]).
• ›The agent explicitly cited external sources in its final response (TechTarget, Yenlo, Wikipedia, LoginRadius, Gartner, Enlyft, 6sense) rather than wso2.com itself, indicating the official site did not surface information in a form the agent could fetch and cite.
• ›The agent identified key gaps it could not fill: customer testimonials (site's /customers page was blocked), exact TCO comparisons, and current 2026 updates—all things that would normally live on the vendor's own site but were inaccessible.
• ›WSO2's own website was entirely non-functional for the agent due to Cloudflare protection; the agent had to pivot to web search and third-party analysis. The site's open-source messaging and multi-product pricing structure were pieced together from external explanations rather than native documentation.
• ›The pricing information came from search result titles linking to specific pricing pages (/api-platform/pricing/, /integration-platform/pricing/) which the agent could not access, forcing reliance on secondary sources (G2, documentation snippets) that provided only partial clarity.