The agent successfully gathered comprehensive, site-sourced answers about Mapbox's product, pricing, and positioning by fetching the homepage, pricing page, Atlas page, and Maps page. The site publishes pricing in structured tables and product descriptions clearly, but omits explicit competitor comparisons and hides some top-tier pricing behind 'contact sales' thresholds; the agent noted these gaps and limitations candidly rather than filling them from external knowledge.

• ›The homepage (step 0) provided high-level product overview and customer examples, typed from memory rather than discovered via site navigation or search—indicating the agent knew the domain but the site doesn't expose canonical entry points in a machine-readable way.
• ›The pricing page (step 1) was highly structured with detailed tiered tables covering all public SKUs, making it content-bearing for the quantitative pricing section; however, many top tiers end with 'contact sales', and the agent noted inconsistent labeling of tier boundaries.
• ›The Atlas page (step 2) and Maps page (step 3) supplied product-specific claims (self-hosting, customization, offline capability, uptime SLA) but neither compared Mapbox to named competitors; the agent correctly reported this absence rather than importing external competitor knowledge.
• ›The agent did not fetch docs.mapbox.com or per-product deep-dives, explicitly acknowledging this scope limitation; the response is therefore summary-level rather than API-complete.
• ›The site's 'contact sales' gates for data products, Atlas licensing, Vision SDKs, and top-tier commercial use (e.g., vehicle, real estate) prevent public pricing disclosure—agent noted this clearly, indicating low friction in discovering what is NOT public rather than guessing.