The agent assembled a comprehensive overview of ProMax Group's business model, target markets, and service offerings, but encountered significant friction: the website's pages returned only obfuscated HTML rather than readable content, forcing the agent to rely on web search snippets and prior knowledge (86% of sourcing) to reconstruct answers about what the company does, who it serves, and how it differs. Pricing information remained largely opaque—no specific figures were found despite searching for pricing pages. The site is poorly navigable for machine agents due to client-side rendering and compression; human-readable content had to be inferred from search metadata and API responses rather than directly fetched.

• ›Direct fetches of promaxgroup.com.vn pages (steps [1], [4], [10], [11], [16]) returned only minified, client-side rendering boilerplate—no actual content. The agent had to work around this by using WordPress REST API endpoints (step [12], [17]) which returned JSON with renderable content, and by relying entirely on web search to surface information.
• ›Web search results (steps [3], [6], [7], [8], [13], [14], [15]) provided the primary source material: search titles and meta descriptions revealed the company operates through subsidiary brands (Smart Choice, Hi-Tech, Global Tech), handles environmental treatment and solar installations, and is based in Da Nang. These were cited directly in the final response as sources.
• ›Pricing information was the largest gap: a search found a pricing page URL (step [14]), but fetching it (step [16]) returned only unreadable HTML. The agent noted 'no specific prices are publicly listed' and had to infer that pricing is custom/project-based from the existence of contact information and the absence of published rates.
• ›The agent had to explicitly note confusion and missing information (differentiation claims, scale, competitive positioning, subsidiary structure) because the website does not publish these details in accessible form—neither in human-readable HTML nor in structured data or meta fields.
• ›The site's Vietnamese-only language and reliance on client-side rendering severely limits agent-readiness; the REST API responses (steps [12], [17]) were the only machine-friendly content layer, but even those required the agent to know the correct endpoint structure.