The agent successfully understood Orb Markets by working around the site's direct access block (429 errors on all orbmarkets.io URLs) and assembling the answer almost entirely from web search results and Helius documentation. The site itself is not directly navigable by the agent, forcing reliance on external sources (blog posts, docs, news articles) to answer what Orb is, who it's for, its pricing model, and how it differs from competitors.

• ›All four content-bearing steps [3, 8, 9, 10] were web searches that returned links to Helius blog posts, documentation, and third-party comparison articles—no direct orbmarkets.io pages were successfully fetched. The agent cited four external Helius-owned sources in its Sources section (Helius blog, Helius docs, eco.com comparison, Bitget news).
• ›The site actively blocks programmatic access via 429 (rate limit) responses on the homepage and all attempted subpaths (/markets, /stake). This forced the agent to rely on prior knowledge (33% per metadata) and web search (67%) rather than discovering the answer directly from the product.
• ›The agent's final answer is coherent and answers all four dimensions of the task (what, who, pricing, differentiation), but is assembled from fragmented external sources rather than a single authoritative product page. Information about staking, API pricing, and data latency remains explicitly unresolved because no primary source was accessible.
• ›Orb's core differentiator (AI-powered transaction explanations) and positioning as a free Solana block explorer were discoverable through external documentation but not from the product site itself, indicating the site is not agent-ready for direct comprehension tasks.