The agent successfully gathered a substantive explanation of Corbits' purpose, audience, governance-first positioning, and why it differs from general agent platforms, drawing from the homepage and feature documentation. Pricing remained unavailable despite targeted attempts, and competitor context required external search since the site itself contains no comparisons.

• ›Homepage and docs.corbits.dev both delivered content-bearing responses with clear feature sets and audience targeting; site is well-structured for documentation but minimal on navigation—most depth requires direct URL knowledge or search discovery.
• ›Pricing is intentionally not published on corbits.dev (attempted /pricing route returned 404), forcing the agent to infer a custom/enterprise model; this is a content gap, not a navigation failure.
• ›Differentiation narrative (cryptographic audit trails, policy hierarchies, credential scoping, model flexibility) came entirely from [8] docs.corbits.dev/features—core positioning is well-articulated but only accessible via documentation subdomain, not homepage.
• ›Agent had to conduct external search [9] to contextualize Corbits against alternatives (Make, LangGraph, Coworker, n8n); the site provides no competitive positioning, so understanding 'how different' required external research.
• ›Site lacks customer case studies, free tier information, and public ROI/comparison tables—all claimed to be present (logoWall references) but not accessible; gaps required model inference rather than fetched content.