The agent successfully gathered a functional overview of Strapi's purpose, audience, and pricing from the official docs and pricing page, but had to work around fragmented, missing, or unclear information about Enterprise features, self-hosting trade-offs, and competitive positioning. The site publishes pricing clearly but leaves licensing boundaries and feature comparisons to external sources or inference.

• ›The pricing page (strapi.io/pricing) was directly fetchable and machine-readable, clearly laying out Cloud tiers, overages, and add-ons per project-month. This was the only resource that answered the pricing question comprehensively.
• ›The docs landing page and Cloud intro page provided product positioning and features, but did not address licensing models (Community vs. Enterprise distinction), Enterprise pricing, or feature matrix — the agent had to note these as missing rather than extract them.
• ›The FAQ page was labeled in navigation but contained no pricing or licensing information, forcing the agent to recognize it as a navigation dead-end and rely instead on other sections.
• ›No fetched page compared Strapi to competitors (Contentful, Sanity, Directus, etc.). The agent correctly identified this gap and did not invent comparisons.
• ›Third-party aggregator sites listed conflicting and outdated pricing (e.g., Developer $29, Team $499, free trials). The agent prioritized the official pricing page over search results, correctly treating external sources as unverified until confirmed on strapi.io.