The agent compiled a comprehensive explanation of Stripe's business model, pricing, and competitive positioning by combining content fetched directly from stripe.com (homepage, pricing, about, payments, connect, docs pages) with web search results about alternatives and fee structures. The site itself provided limited machine-readable detail on pricing tiers and product bundling, forcing the agent to rely heavily on prior knowledge (89%) and external sources to fill gaps—the agent correctly identified several confusing aspects of Stripe's marketing site (lack of clear plan tiers, scattered product ecosystem descriptions, absence of side-by-side feature tables).

• ›The agent fetched stripe.com/pricing [2], stripe.com/payments [7], stripe.com/connect [9], and stripe.com/docs [10] directly but the HTML responses were truncated in the trajectory, so actual content extraction is unclear—the final answer's specific pricing figures (2.9% + $0.30, 0.8% ACH capped at $5, $15 chargebacks) do not appear to come from those fetches and instead derive from web search results [13, 14, 15] and prior knowledge.
• ›The agent guessed most key URLs (stripe.com/pricing, stripe.com/payments, stripe.com/connect, stripe.com/docs) via prior knowledge rather than discovering them by clicking from the homepage—only stripe.com/connect [9] was followed from a link in the /about page, suggesting the homepage navigation did not clearly surface product pages.
• ›Web searches [13, 14, 15] were the primary source for concrete pricing details, competitive comparisons, and market positioning (17.15% market share, $1.05 trillion processed in 2025)—these were not explicitly published on stripe.com's main pages in fetchable form, indicating the marketing site does not centralize this reference data.
• ›The agent correctly flagged what the site made confusing: lack of visible product plan tiers, scattered/siloed product descriptions (Payments, Connect, Billing treated separately), absence of feature comparison tables, and opaque enterprise pricing details—these align with real navigation friction on the site.
• ›The /products URL returned 404 [5] and /use-cases returned 404 [11], suggesting the site's information architecture does not expose an overview page by those common naming conventions.