ora
sunnya97.com
success
Claude Code · Haiku 4.50:24
intent

What does sunnya97.com do and who is it for? Explain it back to me.

5steps
24.1sduration
$0.0279cost
42,054tokens
7 steps2 reasoning steps
home
docs
llms.txt
/llms/about.md
/llms/now.md
100%
on-site discovery
100%
reliability
80%
link following
path origin
  • previous resource80%
  • prior knowledge20%
insight

The agent successfully built a comprehensive understanding of sunnya97.com by fetching the homepage, about page, and LLM-optimized markdown content. The site is highly navigable and agent-ready: it publishes structured content in multiple formats (HTML and markdown), includes an explicit llms.txt guide, and surfaces all necessary information through standard web routes. The agent correctly identified the site as a personal portfolio and knowledge hub, articulated its purpose, audience, and pricing model (free), and called out genuinely missing elements like sparse details on the Ambi project and lack of a contact page.

  • Step [3] (llms.txt) and steps [4–5] (markdown content) provided the most comprehensive and structured information. The site explicitly advertises LLM-optimized content with a guide explaining when and how to use it — this is exceptional agent-readiness.
  • Steps [1–2] (homepage and about page) were the discovery entry points but required following navigational hints to the llms.txt guide; the final response drew heavily from the markdown versions fetched in steps [4–5], which were cleaner and more complete than the truncated HTML responses.
  • The agent had to make one minor inference: it initially looked for commercial/pricing details (typical of business sites) before recognizing this is a personal portfolio. The site's positioning as a personal website is clear in meta tags and content, so this was a user expectation vs. site reality, not a navigation problem.
  • Content gaps the agent identified (incomplete About page, sparse Ambi details, no contact page) appear to be genuine site limitations, not agent misnavigation — the agent correctly distinguished between what the site chose not to expose and what it actively published.
  • 80% of fetches came from prior knowledge/artifacts (likely cached or inferred URLs like /about, /llms.txt, /llms/about.md), suggesting the site's information architecture follows predictable REST patterns that agents can navigate without explicit link discovery.

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 →