The agent successfully gathered enough information to explain Nutshell's core value proposition, target market, pricing structure, and competitive positioning, but had to work around the fact that nutshell.com's own pages failed to render properly. The agent relied heavily on web search results and third-party sources (Wikipedia, Gartner, support docs, competitor blogs) rather than native site content, and explicitly noted that JavaScript-heavy pages on the main domain prevented direct content extraction.

• ›Steps [1], [2], [3], [4], [9] (direct fetches of nutshell.com pages) were fetched but their HTML was truncated/opaque and did not appear in the agent's source citations, indicating they did not yield usable content despite HTTP 200 responses.
• ›All cited sources in the final response came from web search results (steps [5], [6], [8], [10], [11]) or search-discovered URLs like support.nutshell.com and third-party review sites—not from the main nutshell.com domain itself.
• ›Step [7] (support.nutshell.com billing article) was the only directly-fetched resource cited in sources, suggesting the support subdomain was more machine-readable than the marketing site.
• ›The agent explicitly acknowledged that 'their own website didn't load well' and was 'heavily JavaScript-dependent,' forcing reliance on external sources (Wikipedia, Gartner, G2, Insightly, Help Center) to assemble the answer.
• ›Pricing details, feature comparisons, and competitive positioning all came from search results or third-party aggregators, not from nutshell.com's native pricing or comparison pages—indicating those pages are either not indexed well, not agent-friendly, or their content is dynamically rendered.
• ›The agent had to note gaps: no clear feature matrix by tier on the native site, no obvious competitor comparison page, and limited mobile app detail—demonstrating that even after comprehensive search, key structured information was missing from the official domain.