yannis.dev
partial
Claude Code
intent

What does yannis.dev do and who is it for? Explain it back to me.

18steps
98.2sduration
$1.3213cost
152,465tokens
30 steps12 reasoning steps12 searches
home
search
home
search
search
search
/services
docs
/work
search
search
search
search
/contact
search
search
search
search
100%
on-site discovery
33%
reliability
50%
link following
path origin
  • previous resource50%
  • prior knowledge50%
insight

The agent gathered substantial information about Yannis' background, methodology, and project experience but could not fully access complete homepage content or definitively determine service offerings and pricing. The site's homepage HTML was truncated in fetches, and key pages (/about, /services, /contact, /work) returned 404s, forcing the agent to assemble understanding from web search results and prior knowledge rather than direct site content. The agent partially satisfied the task by explaining who Yannis is and his approach, but couldn't definitively answer how the site is monetized or whether services are offered.

  • ›Step [1] and [5] fetched the homepage but returned truncated HTML that did not include readable content sections—only style imports, metadata, and Astro framework scaffolding. The agent noted the presence of a 'model switcher interface' but could not extract substantive text.
  • ›Steps [18] and [21] (web searches) returned the most usable information: a Lovable.dev blog post about Yannis' work and an ETHDenver 2023 award mention. These search results, not the homepage itself, provided the concrete details about his medtech dashboard, e-commerce projects, and agentic loop methodology.
  • ›The site does not publish traditional navigable pages—all attempts to fetch /about, /services, /work, and /contact returned 404s. The agent had to infer structure and content from external references (GitHub profiles, blog mentions, search snippets) rather than from the site's own information architecture.
  • ›The agent's final answer conflates what it found (portfolio showcasing AI-agent methodology) with what it could not verify (whether Yannis actively offers consulting services or is hire-able). The 'model switcher' feature mentioned in the HTML suggests an interactive design, but this was never resolved into actionable information.
  • ›The site is poorly agent-ready: no structured metadata (schema.org, JSON-LD), no llms.txt or robots.txt hints, and key content sections inaccessible via direct fetch. The agent relied 50% on prior knowledge and 50% on previous artifacts (search results), indicating the site itself does not publish machine-readable answers to the task questions.

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 →