What does adyen.com do and who is it for? Explain it back to me.
- previous resource60%
- web search7%
- prior knowledge33%
The agent successfully compiled a comprehensive explanation of Adyen's business model, target market, pricing, and competitive positioning, but had to work around a largely inaccessible website. The Adyen.com domain itself provided minimal structured information (homepage, pricing page, about page all rendered heavily via JavaScript with limited text extraction), forcing the agent to rely on web search results, Wikipedia, and third-party comparison articles to construct the final answer. The site's architecture—with 404s at logical product/solutions URLs and information scattered across multiple portals—made direct navigation nearly impossible.
- ›Steps [1], [3], [8] returned homepage, pricing, and about pages, but these were JavaScript-heavy SPA renders that yielded minimal actionable text in the fetched HTML. The agent could not extract pricing tiers, product details, or audience segmentation from the official pages alone.
- ›Steps [13], [17], [18], [19] were web searches that yielded external comparison articles, Wikipedia, and Adyen's own press releases. These searches were the primary source of substantive claims in the final response (pricing models, competitor comparisons, product names like Capital/Accounts/Issuing, target customer profiles).
- ›Step [15] (Wikipedia) provided historical context and company legitimacy signals but not detailed operational information.
- ›The agent explicitly cited external sources (Chargeflow, ConnectPay, theretailexec.com, Adyen docs portal, press releases) in the final response—not the official website itself. This indicates Adyen.com failed to surface its own value proposition in a way the agent could extract.
- ›Adyen's site is a Nuxt SPA with poor URL structure (/products, /solutions, /developers, /resources all return 404), making traditional sitemap-based navigation impossible. Information architecture is opaque to machine crawlers.
- ›The pricing page exists [step 3, 16] but does not publish actual rates—it requires sales interaction, which the agent correctly noted but could only learn from external comparison content.
- ›The agent's understanding of 'omnichannel positioning,' 'interchange++ pricing,' 'Capital/Accounts/Issuing products,' and 'enterprise target market' came entirely from external sources, not Adyen's own website content.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →