The agent could not fully extract Hexclave's positioning and pricing from the primary domain itself—the fetches of hexclave.com returned JavaScript-heavy HTML that did not render readable content. Instead, the agent relied on a web search [6] that surfaced openalternative.co/hexclave [7], which provided the core framing (open-source Auth0/Clerk alternative). The agent assembled a largely complete answer about what Hexclave does and who it's for, but explicitly acknowledged that specific paid pricing details were not publicly available on the site.

• ›The primary domain (hexclave.com/) returned unrendered Next.js markup—steps [1], [3], [4] were content-empty and did not yield usable text, forcing the agent to pivot to search.
• ›The web search [6] was the discovery lever; its snippet results (particularly openalternative.co/hexclave [7]) provided the missing positioning—'open-source alternative to Clerk, Auth0 and Okta'—that the agent could not extract directly from hexclave.com.
• ›The agent correctly identified and reported gaps: exact paid pricing tiers, feature maturity, deployment docs, and performance benchmarks were not publicly surfaced on the site—only the free tier (10K users) was discoverable.
• ›The site's citation list conflates guessed URLs (hexclave.com/pricing, hexclave.com/blog) with third-party sources (openalternative.co); only the third-party source was actually content-bearing in the trajectory.