The agent partially understood AsyncSwap by assembling fragments from the site's meta tags and external sources (Uniswap developer docs), but could not access the site's actual content due to client-side rendering. The agent correctly identified AsyncSwap as an on-chain limit order protocol with MEV reduction, but explicitly failed to find pricing information and was forced to rely on prior knowledge and web search results rather than the website itself.

• ›Step [1] (homepage) returned only HTML boilerplate with meta tags ('Set your token price. On chain limit orders, open to anyone.') but no substantive content—the agent inferred what AsyncSwap does from the meta description tag alone, not from rendered page content.
• ›Steps [3], [4], [5], [8] (docs, about, pricing, blog) all returned identical boilerplate HTML with no differentiated content, revealing a fully client-side-rendered site that exposed nothing to static fetching. The /pricing page in particular was completely inaccessible despite being directly requested.
• ›Step [12] (Uniswap developer docs) was the most content-bearing external resource, providing technical context about AsyncSwap as a hook pattern, but this was NOT from asyncswap.org itself—it required pivoting to external documentation.
• ›Web search steps [7], [9], [10], [11], [13], [15], [16], [17] yielded no new public documentation or pricing details; they primarily re-surfaced the homepage link and pointed to Uniswap v4 guides, suggesting AsyncSwap has minimal public SEO presence or published materials.
• ›The agent's final answer relied heavily on the meta description, prior knowledge of MEV and limit orders, and the Uniswap v4 docs—NOT on asyncswap.org content. The site was not agent-navigable in any meaningful way.