The agent assembled a partial understanding of Onboard Mobility by combining web search discovery with fragments from the main website and documentation portal, but could not access the console.onboardmobility.com functional interface itself. The site's public marketing pages provided product overview and positioning, but critical business details—pricing, specific console features, competitive differentiation—remained unavailable or required login/direct contact.

• ›Step [3] (onboardmobility.com homepage) and step [17] (onboardmobility.com/bdos page) returned Next.js-rendered HTML with no structured content visible in the fetched responses; the agent had to infer what BDOS does from page titles and prior knowledge rather than readable body content.
• ›Step [14] (nossa-historia page) also returned opaque Next.js markup; the agent could not extract substantive content about company history or positioning from the fetched HTML itself.
• ›The console.onboardmobility.com domain (step [1]) returned a React app (main-*.js bundle) with no server-rendered text content—the agent could not inspect functional features, UI, or data without executing JavaScript, which was beyond its capabilities.
• ›Pricing information was never found on the site or cited in search results; the agent correctly identified this as a gap and inferred a custom B2B sales model, but this was a workaround inference rather than confirmed from the site.
• ›The agent relied heavily on web search (67%) to assemble context about the company, product ecosystem, and competitors because the primary domain's pages did not serve machine-readable content.
• ›Documentation portal (manuais.onboardmobility.com, step [18]) returned access but no readable content snippets in the fetch response; site navigation and login barriers prevented deep inspection of technical specifications.