ecoos.co
success
Claude Code
intent
What does ecoos.co do and who is it for? Explain it back to me.
8steps
43.5sduration
$0.4510cost
93,894tokens
13 steps5 reasoning steps2 searches
home
docs
/features
docs
search
/software/eco-os-reviews
search
/eco-os/competitors
67%
on-site discovery
17%
reliability
50%
link following
path origin
- previous resource50%
- web search33%
- prior knowledge17%
insight
The agent partially satisfied the task by assembling a coherent overview of ECO-OS from the homepage and web search results, but had to work around severe gaps in the site's transparency. The homepage provided high-level positioning (what it does, who it's for), but the site offered no public pricing, no dedicated feature pages, and no comparative positioning — forcing reliance on prior knowledge and external sources to construct differentiation claims and pricing estimates.
- ›Step [1] (homepage) was the only successful fetch from ecoos.co itself; it contained meta descriptions and likely rendered content defining ECO-OS as a 'sustainability software suite' for ESG reporting and data-driven decisions, but the agent's final response shows it extracted only high-level positioning, not detailed feature lists or use cases.
- ›Steps [3–5] (pricing, features, about pages) all returned 404s, indicating the site is minimally navigable — the agent had to guess at standard URL patterns and failed. The site does not surface internal architecture or content discovery paths.
- ›Steps [7] and [10] were web searches that returned search result snippets and URLs but no readable content (external sites returned 403 blocks). The agent cited search results as sources without being able to fetch them, indicating it relied on search snippet metadata and prior knowledge to generate competitive comparisons (EcoVadis, Greenly, Sweep, Workiva, Persefoni) rather than from actual fetched content.
- ›Pricing, implementation details, integrations, and customer case studies — all critical for the discovery-evaluation task — are entirely absent from the site and unavailable via search. The agent explicitly flagged this gap in its response ('I couldn't find specific pricing information').
- ›The site's agent-readiness is low: no structured data (schema.org), no sitemap, no alternative entry points, and a static Framer-built site that does not expose navigation or content hierarchy in a machine-readable way. The agent had to rely on prior knowledge (33% web search, 17% prior knowledge, 50% previous artifact reuse per metadata) to fill gaps.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →