The agent successfully assembled a comprehensive explanation of Dex's offering by combining direct site fetches (homepage, about, pricing, product overview, integrations pages) with web search results that filled gaps the site's client-side rendering left unfilled. The site was partially navigable—its structure and sitemap were discoverable, but pricing and feature details required JavaScript rendering that the agent couldn't fully parse, forcing reliance on third-party reviews and GitHub gists for concrete pricing tiers and plan comparisons.

• ›The sitemap (step 9) was critical—it revealed the pricing page URL that earlier direct guesses had missed (/pricing/ exists; /plans does not), and gave the agent a complete picture of available pages. Without it, pricing details would have been entirely inaccessible.
• ›The homepage, about, and product overview pages (steps 1, 4, 12) loaded but returned only React shell HTML with no rendered content visible in the raw responses—the agent cited them as sources but had to rely on meta tags and prior knowledge to extract meaning. The actual content was client-side rendered and invisible to the agent.
• ›Web search results (steps 15, 16, 18, 20, 22) were the primary source of concrete, actionable details: pricing tiers ($12/mo premium, $20/mo monthly), plan limits (2,500 vs. 9,000 contacts), and differentiators vs. competitors. The agent sourced these from third-party review sites (GetApp, SaaSWorthy), GitHub gists, and Dex's own blog comparisons—not from its own website's pricing page.
• ›The /pricing page (step 11) was fetched but returned only the HTML shell without rendered pricing tables or tiers, confirming the site's pricing information is not machine-readable without JavaScript execution.
• ›The agent was transparent about gaps: Professional tier exact pricing, detailed AI feature capabilities, and contact limit thresholds across specific plans remained ambiguous even after multiple targeted searches.
• ›The site is moderately discoverable (clear domain, functional sitemap, published blog content) but poorly agent-navigable—critical decision-making information (pricing, plan features) is locked behind client-side rendering, forcing agents to bridge the gap with external sources.