The agent successfully gathered enough information to explain what Zyberspace does, who it's for, and how it differs from alternatives, but pricing information remained largely inaccessible. The agent discovered that Zyberspace publishes machine-readable documentation via llms.txt, openapi.json, and MCP server metadata, but the main website relies on JavaScript rendering that obscured pricing details and marketing messaging that contradicts the actual product positioning.

• ›Steps [10], [11], and [14] were content-bearing and directly cited: llms.txt provided clear product definition ('Instant static site hosting for developers and AI agents'), openapi.json confirmed the same messaging, and the MCP server card explained AI agent integration. These were discovered via prior knowledge (guessed URLs), not surfaced from the homepage.
• ›Step [21] (sitemap.xml) was cited and showed that pricing, product, and other pages exist, but attempts to fetch their HTML content (steps [4], [19], [23], [24]) all returned truncated JavaScript-heavy responses that did not expose readable pricing or feature details.
• ›The site publishes developer-friendly machine-readable artifacts (.well-known/ endpoints, llms.txt, openapi.json, sitemap.xml) that are highly agent-ready, but the marketing-facing pages (homepage, pricing, product) are JavaScript-rendered SPA pages that are effectively opaque to HTML scraping. This created a two-tier discoverability: agent-native docs are clear, but human-facing marketing is inaccessible.
• ›A critical usability gap: the homepage meta description claims 'Generate, edit, and publish a mobile-friendly business website' and mentions 'lead forms website' (implying a website builder), but the actual product is a static site hosting platform for already-built sites. The agent noted this mismatch as a source of confusion.