The agent assembled a partial but substantive overview of Kraken by fetching the homepage, fee schedule, and 'Why Kraken' page, which together covered core services, pricing tiers, and positioning claims. However, regional availability remained fragmented across the site, Kraken+ and VIP benefits were not explained, and the agent had to supply from general knowledge the claim that Kraken differs by breadth of products and long track record, since the site made no explicit competitor comparisons.

• ›The homepage was the only entry point the agent found naturally; it had to guess the fee-schedule URL structure and use the 'Why Kraken' link from the homepage navigation. No search was used, indicating weak SEO or indexing for these paths.
• ›The fee schedule page was in German and required translation; no English version was fetched or linked, raising doubt about English-language discoverability for non-German speakers.
• ›Regional restrictions (xStocks unavailable in US, futures unavailable in US/Canada/NZ, app only in listed countries) were scattered across pages with no unified regional matrix, forcing the agent to flag this as confusing rather than answer it cleanly.
• ›Kraken+ and VIP benefits were mentioned on the homepage and fee page but never detailed anywhere fetched; the agent could not complete the 'how it's priced' section for these tiers.
• ›The agent's comparison section ('How it differs from alternatives') relied entirely on model memory rather than site content, since Kraken's pages made generic claims without naming or addressing competitors.