ora
kuruhu.com
success
Claude Code
intent

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

11steps
46.8sduration
$0.3903cost
90,153tokens
17 steps6 reasoning steps2 searches
home
/features
/manifesto
search
/showcase
docs
search
llms.txt
docs
docs
docs
100%
on-site discovery
89%
reliability
78%
link following
path origin
  • previous resource78%
  • prior knowledge22%
insight

The agent successfully assembled a comprehensive understanding of kuruhu by fetching the homepage, features page, manifesto, showcase, blog index, llms.txt, and two comparison articles. The site is well-navigable for discovery purposes: it publishes a machine-readable llms.txt summary, maintains comparison articles against competitors, and surfaces key positioning through editorial content. However, pricing information was not explicitly documented—the agent correctly identified that kuruhu is free but had to infer this from multiple pages rather than finding a dedicated pricing page, and custom domain availability required reading between the lines from comparison articles.

  • Step [12] (llms.txt) was the single most valuable fetch—it provided a structured, comprehensive definition of what kuruhu is, who it's for, and core features in machine-readable form. This is exemplary agent-friendly design.
  • Steps [14] and [15] (comparison articles vs. Linktree and 21 alternatives) were essential for understanding differentiation and pricing relativity, but required the agent to read detailed blog posts rather than consuming a simple pricing table. The site publishes these as full HTML articles, not structured data.
  • Pricing was genuinely missing from the site's IA: step [6] returned a 404 for /pricing. The agent had to synthesize 'completely free' from the homepage claim 'No credit card' (visible in step [1] meta tags) and contextual information scattered across comparison articles. This represents a navigability gap for users seeking quick pricing answers.
  • Steps [3], [4], [9], [10] (features, manifesto, showcase, blog) were all discoverable from the homepage and site navigation, showing good internal linking, but required multiple fetches to assemble the full picture. The site prioritizes narrative exposition over structured reference documentation.
  • The agent correctly identified that custom domains were 'on the way' and that several implementation details (contact form features, analytics granularity, account recovery procedures) were not documented—these are true gaps in transparency, not agent limitations.

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 →