The agent assembled a comprehensive explanation of Mindbox by combining fragments from the site's JavaScript-heavy pages, web search results, and prior knowledge. The site proved challenging to parse: key pages like homepage, about, CDP product, and tariffs all loaded but rendered primarily through JavaScript, making structured content unavailable in raw HTML. The agent successfully answered what Mindbox does, who it serves, and how it differs from competitors, but could not extract exact pricing details or feature matrices because those were hidden behind client-side rendering.

• ›The homepage [1], about page [5], CDP product page [13], and tariffs page [19] all returned 200 status but truncated HTML with no visible table or structured pricing data—only metadata and CSRF tokens. The agent had to rely on web search snippets and prior knowledge to fill in the gaps.
• ›The English-language mirror site mindbox.cloud [16] was fetched but also returned minimal HTML content in the response, indicating the same JavaScript rendering issue across both domains.
• ›The agent correctly inferred Mindbox's market position, customer base, and omnichannel focus from metadata, search results, and external review sites (SelectHub, CDP Solutions, Crunchbase), but could not retrieve actual tariff tiers, module costs, or free trial availability from the official site itself.
• ›A direct guess for /features [4] returned a 404, indicating the site does not organize features on a dedicated page; the agent had to hunt for product information via search results pointing to /products/cdp instead.
• ›The agent cited the homepage, about page, CDP product page, and tariffs page in its sources despite those pages returning minimal extractable content—suggesting the agent treated them as 'visited' rather than 'read' and relied on search-sourced intelligence to build the final answer.