What does emcasa.com do and who is it for? Explain it back to me.
- previous resource50%
- web search13%
- prior knowledge38%
The agent assembled a coherent explanation of EmCasa by combining fragments from the live homepage and 'About' page with external sources (web search results and cited articles). The site itself was minimally navigable—most of the core information gaps (pricing details, seller workflows, neighborhood coverage, current status) could not be filled by direct website navigation, forcing heavy reliance on prior knowledge and external reporting. The final answer is substantive and well-sourced but represents a workaround rather than direct, transparent disclosure from the site.
- ›Steps [1] and [3] (homepage and /sobre page) returned HTML but were heavily JavaScript-rendered; the agent extracted minimal semantic content directly and fell back on prior knowledge and web search to fill gaps. The actual page content was not accessible in the fetched responses.
- ›Steps [10], [11], [16], and [17] (web searches) were the primary source of factual claims—commission rates (5-6%), salaried agent model, AI integration, R$110M funding, and competitive positioning. These search results cited external news sources (Exame, InfoMoney, Bloomberg Línea) rather than EmCasa's own documentation.
- ›Critical information was missing or 404'd on the site itself: seller workflows (/como-vender, /vender both returned 404s in steps [4], [6], [13]); pricing pages (/tabela-de-precos returned 404 in step [7]); how-it-works (/como-funciona returned 404 in step [8]); partnerships (/parceria returned 404 in step [14]). The site does not publish this information in a directly fetchable form.
- ›The agent could not determine current geographic coverage, recent business updates, or detailed service scope from the site alone. The most recent funding news cited (R$110M, 2021) and expansion (11 cities) came from external sources, not the company's own channels.
- ›The site is built on Next.js with heavy client-side rendering, making it opaque to automated parsing. No structured data (schema.org, JSON-LD, meta tags) was evident in the fetched responses that would clarify business model, pricing, or service areas.
Help the next agent finish on emcasa.com
Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.
or talk to us about agent readiness →