The agent gathered a coherent overview of Onboard Mobility despite the site's limited navigability. The main website pages were either JavaScript-rendered with no accessible text content (steps 1–5, 12–14) or returned 404s (steps 3–5), forcing heavy reliance on external sources (LinkedIn, news articles, Microsoft AppSource) discovered via web search. The agent successfully assembled what Onboard Mobility does, who it serves, and key product features, but could not extract pricing information or a detailed customer list from the official site itself.

• ›Steps 1–5 and 12–14 fetched the official website but returned only HTML scaffolding with no readable content—the site is built on Next.js and renders content client-side, making it invisible to server-side fetches. This forced the agent to pivot entirely to external sources.
• ›Step 9 (LinkedIn company profile) and step 21 (site-specific search result) provided the most actionable content: company founding date (2015), location (São Paulo), and product names (DBD, BDOS, Bipay). These were the only official-adjacent sources that yielded structured information.
• ›The agent discovered product pages (/bdos, /cases, /whatsapp in steps 12–14) and attempted to fetch them, but received no readable content—indicating the site's navigation structure exists but content is not server-rendered, making the site effectively unnavigable to a bot without JavaScript execution.
• ›Pricing information was explicitly not found anywhere on the official site (404 to /pricing in step 3, no pricing details in any subsequent fetch). The agent correctly identified this as a gap and noted it requires direct sales contact—a reasonable inference for B2B enterprise software.
• ›The agent cited LinkedIn, Visa news article, ZoomInfo, and Microsoft AppSource as sources, not the official website itself—a sign that onboardmobility.com does not publish its own usable content in bot-readable form. The site functions as a landing page / portal rather than a content repository.