The agent assembled a comprehensive explanation of Wise by combining direct site fetches (homepage, pricing pages for multiple regions, about page, business account page) with targeted web searches about fees, competitors, and alternatives. The site itself is React-heavy and renders dynamically, making shallow crawls uninformative; the agent relied heavily on prior knowledge and external sources (blog posts, comparison guides) to answer the task. Despite these navigation constraints, the agent successfully delivered a detailed, well-sourced breakdown of what Wise does, who it's for, pricing structure, and differentiation.

• ›Steps [0], [3], [4], [5], [9] fetched the site directly but returned truncated React app shells with minimal rendered content visible in the HTTP response. The agent could not extract detailed feature or pricing information from these responses alone.
• ›The agent pivoted to web search (steps [7], [8], [10]) and explicitly cited external sources in the final response — including Wise's own blog comparison pages (/blog/alternatives-to-wise, /blog/remitly-competitors) and third-party fee guides. These external sources provided the substantive pricing details and competitive positioning that the main site pages did not expose in a crawlable form.
• ›Wise publishes structured information (pricing, competitors, alternatives) but gates it behind JavaScript rendering and organizes it across region-specific URLs (/us/pricing, /gb/pricing) and blog content rather than a single definitive pricing or features page. The agent had to discover these through navigation patterns and search.
• ›The agent was transparent about what it could not find (max transfer limits, business pricing details, payment method options, support structure) — these were blocked by the React rendering or simply not prominently linked. The 404 on /features (step [2]) is emblematic.
• ›Wise's business account offering (step [9]) and comparison content (step [10] search results pointing to /blog/alternatives-to-wise) were discoverable but required either specific URL guessing or search redirection to surface. The site does not appear to have a top-level navigation path that guides visitors to comprehensive competitive positioning.