athaus.ai
partial
Claude Code
intent
What does athaus.ai do and who is it for? Explain it back to me.
21steps
125.7sduration
$1.9140cost
453,615tokens
25 steps4 reasoning steps12 searches
home
/de
docs
/en
search
docs
/manifesto
search
search
search
/profiles/company/1390…
search
/careers
search
search
search
/post/how-athaus-ai-is…
search
search
search
search
44%
on-site discovery
78%
reliability
11%
link following
path origin
- previous resource11%
- web search56%
- prior knowledge33%
insight
The agent gathered a coherent explanation of Athaus's core value proposition (AI-native real estate automation, full-stack transaction orchestration, German-focused valuation engine) but could not locate explicit pricing, detailed business model, or customer case studies. The site itself is German-language, server-side rendered, and did not expose readable content during direct fetches; the agent relied on web search results and a third-party article (soonami.io) to construct most of its answer, working around the inaccessible primary source.
- ›Steps [8], [9], and [19] (direct fetches to /about, /manifesto, /careers) all returned truncated HTML with no readable text content — the site is a Next.js application with client-side rendering that did not serve content in the HTTP response body, making it invisible to the agent's direct navigation.
- ›The agent's substantive answer came primarily from web search (step [7], [10], [12], [14], [16], [17], [18], [20], [21], [22]) and one third-party article (step [23], soonami.io), not from the official site. The Athaus domain itself functioned as a pointer to resources rather than a source of information.
- ›Critical information gaps (pricing, business model, service delivery method, geographic scope, B2B vs. B2C positioning) were explicitly identified by the agent as missing — no pricing page exists, no public commission rates were found, and the site does not publish structured data or clear CTAs that would guide an agent to next steps.
- ›The site's German-language default and lack of English fallback limited discoverability; the agent had to infer from external sources that Athaus is Berlin-based and Germany-focused, rather than this being stated in a machine-readable or easily parsed form on the primary domain.
- ›Site navigability was poor for both human and agent: direct fetches returned no usable content (server-side rendering issue), structured metadata or schema.org markup was not evident in the truncated responses, and no pricing, FAQ, or case study pages were accessible or discoverable.
Help the next agent finish on athaus.ai
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 →