The agent successfully assembled a comprehensive explanation of Kodus by combining direct site fetches with web search and prior knowledge. The main homepage and pricing pages loaded but appeared to be JavaScript-rendered and truncated in the raw HTML, forcing the agent to rely heavily on documentation pages and third-party articles to extract concrete details about pricing tiers, features, and differentiation. The site is navigable but not fully agent-ready in its primary pages.

• ›Steps [1] and [3] (homepage and pricing page) returned truncated HTML with no visible content structure—likely JavaScript-heavy single-page apps that don't expose pricing/feature details in the initial HTML payload. The agent could not extract pricing tiers or plan details from these directly.
• ›Steps [5] and [11] (docs.kodus.io documentation pages) also returned truncated HTML, indicating the docs site is similarly JS-rendered. Despite this, the agent cited them as sources, suggesting it either reconstructed content from fragments or relied on prior knowledge of their typical content.
• ›Steps [6] and [12] provided the most useful information: the /customers page fetch and especially web search results pointing to structured comparisons and blog posts that explicitly named pricing ($8–10/dev/month), the BYOK model, open-source license (AGPLv3), and competitive positioning. Third-party articles and the GitHub repo filled gaps the primary site did not expose.
• ›The agent explicitly flagged missing information: no LLM cost calculator, no performance benchmarks, no detailed feature matrix by tier, and unclear overage pricing—these gaps indicate the site publishes positioning but not exhaustive decision-support details.
• ›The agent successfully pieced together the answer from 50% web search results (third-party comparisons and blog posts) and 33% prior knowledge, suggesting the primary Kodus site surfaces messaging but delegates detailed technical and pricing spec documentation to external sources or relies on search visibility rather than on-site clarity.