The agent assembled a comprehensive explanation of Frontify by combining technical documentation from the GitHub Pages site with product and pricing information sourced entirely from web search and prior knowledge. The frontify.github.io domain itself is poorly navigable—the root returns a 404, and the site offers no introductory content, pricing, or competitive positioning; the agent had to construct the full picture by searching for the main Frontify website and third-party sources.

• ›Steps [6] and [7] confirmed that frontify.github.io hosts GraphQL API reference and a public API explorer, but these pages are purely technical specifications with no context about what Frontify does or who uses it—the agent correctly identified this as a significant gap.
• ›Steps [3] and [4] were routing searches that pointed the agent to specific paths on frontify.github.io (graphql-reference, public-api-explorer) and GitHub repositories (Fondue design system, brand-sdk), but the site did not surface discovery-layer content; the agent had to know or guess these URLs existed.
• ›Step [9] and prior knowledge provided all answer content about what Frontify is, pricing, and competitive positioning—none of this information appears on frontify.github.io itself. The agent explicitly noted in its final response that pricing 'isn't on the developer site at all' and the site doesn't compare itself to competitors.
• ›The site is structured as a pure technical API portal with no landing page, onboarding, or business context—it assumes visitors already know what Frontify is and why they need to integrate with it. This is agent-hostile for discovery and identity tasks.