The agent successfully assembled a comprehensive explanation of Dakota's business, audience, and positioning by combining documentation fetches with web search results, but encountered significant gaps in pricing transparency. The site's core product information (stablecoin infrastructure, API flows, compliance features) was accessible via docs, but pricing details were intentionally hidden behind a sales-gated model, forcing the agent to rely on external sources and infer the business model. The agent delivered a satisfactory answer despite this friction, clearly documenting what could and could not be found.

• ›Steps [3], [4], [5], [6] returned structured technical documentation (llms.txt index, Get Started guide, Common Flows, Terminology) that clearly explained Dakota's five core workflows and positioning. This content-bearing documentation provided the factual foundation for 'what Dakota does' and 'who it's for.'
• ›Steps [15], [16], [17] were web search results that surfaced press releases, news articles, and competitive comparisons from external sources (PR Newswire, Morningstar, CoinDesk, Eco Support, Bridge case study). The site itself does not publish competitive positioning or funding announcements — the agent had to search externally to construct the 'how it's different' section.
• ›The `/pricing` page (steps [1], [14]) returned HTML that redirects to the homepage and contains no pricing detail. The agent correctly identified this gap and noted that specific transaction and service fee amounts are not publicly disclosed, requiring a sales conversation. This is a deliberate design choice that makes the site less agent-navigable for discovery tasks.
• ›The site has no `/about-us`, `/news`, or competitive comparison pages with machine-readable content — steps [11], [12] fetched these URLs but returned only HTML without text content in the trajectory. The agent relied on external press coverage and the Gen.xyz blog post (found via web search) to learn about founder Ryan Bozarth and the Series A funding.
• ›Documentation (docs.dakota.xyz) was well-structured and accessible, but forward-facing marketing pages (dakota.xyz/*) were not returned with parseable text content, suggesting they are rendered client-side. The agent's final response cites the marketing homepage and docs as sources, but the HTML responses shown are truncated and do not reveal what text the agent actually extracted.