The agent partially assembled a usable explanation of MDX Studio by pivoting from the inaccessible app login page to the public marketing site and llms.txt file. The company site provided core positioning (WhatsApp customer service, automation, shared inbox) and one vertical (medical clinics), but omitted pricing, technology details, competitor context, and interface access—forcing the agent to call out substantial gaps rather than deliver a complete picture.

• ›The app.mdxstudio.com.br URL (the requested domain) returned only a title with no product description, login UI, or navigation—the agent had to leave this domain entirely and infer its purpose from the public site.
• ›The marketing site (mdxstudio.com.br) provided the core narrative: WhatsApp automation, shared inbox, official API, and medical clinic positioning, but published no pricing, plan tiers, or implementation cost clarity—making it sales-led and opaque to self-evaluation.
• ›The llms.txt artifact (step [3]) confirmed and slightly expanded the marketing site's claims (Meta Tech Provider status, Brazilian location, no public API) but added no new substantive facts beyond what the homepage already stated.
• ›The agent correctly flagged that the product calls itself 'secretária digital' (digital secretary) without disclosing whether it uses AI or rule-based automation, and marked the demo chat as fictional—both material gaps for evaluation.
• ›Navigation was straightforward (internal links led to subpages and company info), but the site structure did not surface pricing, a product walkthrough, or login/demo access in the fetched content, so the agent had to infer those are sales-gated.