The agent successfully assembled a comprehensive overview of Shipmnts by combining web search routing with content from the official website and blog. The site's marketing pages contained product positioning, features, and customer segments, but pricing information was intentionally opaque and required disclosure that sales contact was necessary. The agent had to work around JavaScript-rendered SPA content at app.shipmnts.com itself and rely heavily on search-discovered blog posts and product pages to construct the full picture.

• ›Step [4] (shipmnts.com/) and [6] (shipmnts.com/us) returned only HTML scaffolding with no readable content—both are client-side rendered SPAs that require JavaScript execution. The agent could not extract meaningful information from the direct app domain fetch [1].
• ›Steps [13] (shipmnts.com/us/products/forwarding/) and [21] (search result pointing to real-time P&L blog post) were the primary content sources. The forwarding product page and the blog article on real-time P&L visibility provided concrete feature descriptions, financial metrics claims, and use-case positioning.
• ›Pricing is deliberately hidden behind a sales contact wall—no public pricing page exists. The agent correctly identified this as a gap and noted it requires direct outreach, flagging it as a notable friction point for evaluation.
• ›The agent relied on web search (67% of fetches) to discover landing pages and blog content that static website structure would have surfaced. Direct navigation to the app failed due to SPA rendering; discovery happened through search routing, not site navigation.
• ›The site exposes target customer types (freight forwarders, NVOCCs, 3PLs), key features (real-time P&L, document automation, tracking), and competitive positioning through marketing copy, but does not publish structured product data, API documentation, integration ecosystem details, or roadmap timelines in a machine-readable format.
• ›Security claims and compliance features (AMS, ISF filing) are mentioned in blog/product context but not formally documented. The agent had to note these as 2026 roadmap items from blog content rather than official feature matrix.