The agent assembled a comprehensive explanation of Strapi by combining shallow fetches from strapi.io (homepage, pricing, features, demo pages) with four targeted web searches that returned detailed third-party articles about Strapi's positioning, pricing tiers, and competitive comparisons. The site itself uses client-side rendering and does not expose detailed content in HTML form, forcing the agent to rely on prior knowledge (43%) and external sources (57%) to answer all four required questions (what, who, price, differentiation). The agent successfully fulfilled the task despite the site's limited machine-readability.

• ›Steps [1, 2, 3, 8] returned mostly HTML scaffolding due to client-side rendering; the agent could not extract core content directly from strapi.io. The pricing page [2], features page [3], and demo page [8] all loaded but yielded no visible information in the fetched response.
• ›Steps [10, 11, 12, 14] were all web searches that returned third-party articles. These searches were content-bearing: they surfaced articles comparing Strapi to Contentful/Sanity (step 12), explaining pricing tiers (step 11), and defining use cases (step 14). The agent explicitly cited sources from these searches in its final response.
• ›The agent worked around the site's client-side rendering limitation by pivoting to external search results. No content from strapi.io itself was directly cited in the final response's source list—all citations point to external blogs and comparison sites. This indicates Strapi's marketing site does not publish comparison tables, pricing details, or positioning statements in a directly fetchable form.
• ›The agent identified three specific gaps in what the site communicates clearly: (1) the distinction between self-hosted (free) and managed (paid) tiers is not obvious on first visit, (2) 'headless CMS' terminology is assumed rather than explained, and (3) feature/limit differences between cloud tiers (Essential/Pro/Scale) are not publicly detailed. These gaps suggest the site prioritizes visual design over semantic clarity for agents and non-technical users alike.
• ›The friction outcome 'succeeded_with_light_bridge' reflects the agent's need to bridge a gap: it successfully completed the task by supplementing thin direct fetches with external research, rather than assembling the answer primarily from strapi.io itself.