The agent assembled a mostly complete answer about Wafflebase by retrieving its GitHub README and license, but had to work around a nearly blank marketing website and the absence of any pricing or business model information. The site's dynamic React architecture and lack of traditional content pages (pricing, about, feature comparisons) forced heavy reliance on the GitHub repository and prior knowledge; pricing in particular remains genuinely missing, not just hard to find.

• ›Step [24] (raw.githubusercontent.com/wafflebase/wafflebase/main/readme.md) was the primary content source, providing the product description, feature list, technology stack (Yorkie CRDT, canvas rendering), and explicit status ('early development, not production-ready'). Step [26] confirmed Apache 2.0 open-source licensing, directly answering the 'how it's priced' question: free and open-source.
• ›The main website (step [1]) is a React SPA with no extractable content in the HTML head/initial markup. Routing attempts to /pricing, /about, /features all returned 404s or SPA redirects (steps [3], [4]), forcing the agent to infer positioning from documentation and GitHub. No pricing page, no team page, no business model statement exists in any fetchable form.
• ›The agent's final response acknowledges three hard gaps: (1) no clear business model or monetization path despite open-source status, (2) no founder/team information discoverable, (3) production-readiness concerns. These are not agent failures but genuine absences on the site—the README itself states 'Core spreadsheet and document editing features work, but the project is not yet production-ready.' The agent correctly flagged these as confusion points rather than presenting incomplete data as answers.