The agent could not access the preview deployment directly (steps [1], [3], [9], [10], [11] returned unreadable compressed HTML), so it pivoted to web search and fetched the production ethconf.com site instead. The agent successfully assembled a reasonably complete overview of ETHConf's purpose, audience, and differentiation from alternatives, but pricing information was incomplete (founder pass exact pricing not found), and it explicitly flagged inability to see what the preview branch specifically contains. The site's content exists but required heavy reliance on search results and the production domain rather than the target preview URL.

• ›Steps [5], [13], [15], [16] (web searches) were content-bearing: search result snippets and linked URLs contained explicit information about ETHConf's positioning (5,000+ attendees, 3-day conference, NYC, June 2026), ticket pricing ranges ($399–$1,099), and differentiators vs. EthCC and Devcon.
• ›Steps [6] and [14] (fetches to ethconf.com/ and ethconf.com/tickets) were cited as sources but returned compressed HTML; the agent relied on *search result snippets and URL surfacing* rather than parsing the actual page content from those fetches.
• ›The target preview URL (steps [1], [3], [9], [10], [11]) was inaccessible in readable form — all returned the same truncated, minified HTML with no visible body content. The agent never found what the 'conf27-launch' feature branch adds or changes.
• ›Agent-readiness: The site structure exists (ethconf.com is navigable, has /tickets, /about, /pricing routes) but is not machine-friendly via the preview deployment. Production site content is gated behind HTML rendering, not exposed as JSON/structured data. Search engines and prior knowledge were more useful than direct page fetches.
• ›Pricing information is partially incomplete: standard tiers and early-bird discounts are documented, but 'founder pass' exact pricing is explicitly not publicly listed, and the agent acknowledged this gap.