The agent successfully pieced together a comprehensive explanation of Kong by discovering that the requested domain (kong.com) was a parked page and pivoting to the correct site (konghq.com), then fetching product pages, pricing information, and AI Gateway details. The site was moderately navigable once the correct domain was identified, with product pages accessible via direct URL guesses and search results, though pricing details and feature differentiation required assembly from multiple pages and external comparisons rather than a single, authoritative resource.

• ›The agent discovered kong.com was a dead end (parked page redirecting to /lander) and used web search to identify konghq.com as the canonical domain—this pivot was critical and required search-assisted discovery rather than site navigation.
• ›Product pages (Kong Gateway, Kong Konnect, Kong AI Gateway) returned content-bearing HTML via direct URL guesses (/products/kong-gateway, /products/kong-konnect, /products/kong-ai-gateway), indicating predictable URL structure but no visible site navigation or index to discover these offerings.
• ›Pricing page (konghq.com/pricing) was fetched directly but the agent had to supplement it with external sources (Zuplo, TrueFoundry, WSO2 comparisons) because Kong's published pricing was incomplete—enterprise tiers show 'contact sales' rather than transparent rates, forcing reliance on third-party analysis.
• ›The agent cited six external sources (Zuplo, WSO2, TrueFoundry, Kong blog posts) alongside four Kong pages, indicating that Kong's own site does not comprehensively answer competitive positioning or detailed pricing questions—the site lacked structured competitive data and cost breakdowns.
• ›Product naming and feature overlaps (Kong Gateway vs. Kong Enterprise vs. Konnect) were noted as confusing; the site exposes these as separate product pages but does not clearly diagram how they relate or when to choose each, requiring the agent to infer from fragments.
• ›AI Gateway semantic caching features were found via blog posts rather than dedicated feature pages, suggesting newer capabilities are not yet well-indexed or summarized on primary product pages.