The agent assembled a comprehensive answer about WunderGraph's purpose, target audience, pricing, and differentiation from Apollo, but had to work around the site's heavy client-side rendering, which blocked access to key pages (/features, /docs) and prevented direct extraction of pricing details and feature matrices. The agent relied heavily on web search results and third-party sources to fill gaps left by the site itself, ultimately succeeding in the task despite the site's poor machine-readability.

• ›The homepage [1], pricing page [3], Cosmo page [9], and self-hosted page [21] all returned HTML but were client-side rendered (Next.js), making actual content inaccessible without JavaScript execution; the agent could not extract structured pricing tiers or feature details directly from wundergraph.com itself.
• ›Web search results [11, 14, 18, 19, 20] were the primary source of concrete information about the product's capabilities, positioning, and pricing tiers—these search snippets and third-party comparison sites (plainenglish.io, peerspot.com, thenewstack.io, GitHub README) contained the factual content the agent needed, not the official site.
• ›The agent correctly identified that WunderGraph offers both open-source (Apache 2.0) and managed cloud tiers, but could not verify exact pricing ($499, $999) or feature boundaries directly from the site's pricing page—this information came entirely from web search and external sources, indicating the site does not publish pricing in a machine-readable or plain-HTML form.
• ›Direct navigation attempts to /features and /docs returned errors [4, 8], suggesting either URL mismatches or pages that only render client-side; the agent had to infer feature details from comparison pages and GitHub documentation rather than official feature documentation.
• ›The site's positioning is somewhat muddled across the homepage, Cosmo landing page, and use-case pages—the agent noted confusion about whether 'WunderGraph' refers to the original platform or Cosmo specifically, a problem the site's structure did not clearly resolve.