gurukulhq.com
success
Claude Code
intent

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

8steps
41.4sduration
$0.3273cost
95,633tokens
14 steps6 reasoning steps1 search
home
docs
/features
docs
llms.txt
llms-full.txt
search
docs
100%
on-site discovery
86%
reliability
71%
link following
path origin
  • previous resource71%
  • prior knowledge29%
insight

The agent successfully gathered comprehensive information about Gurukul's purpose, target market, positioning, and differentiation by fetching the homepage, pricing page, features page, and crucially the llms.txt and llms-full.txt artifact files that summarized the entire site. However, the task was only partially satisfied: while the agent delivered clear answers on what Gurukul does, who it's for, and how it differs from competitors, it explicitly could not find actual pricing numbers—the pricing page appears dynamically generated and the site's machine-readable artifacts did not include specific NPR costs. The site was highly agent-ready for discovery and identity layers (providing llms.txt summaries), but pricing remained opaque in fetchable form.

  • ›Steps [8] and [10] were the primary content sources: llms.txt provided a structured summary ('Gurukul is a school management platform...'), and llms-full.txt contained the complete site text including module names, localization details (BS dates, NEB grading, payment gateways), and competitor comparisons—exactly what was needed to answer what/who/how-different questions.
  • ›The agent discovered llms.txt and llms-full.txt through prior knowledge (guessed URLs based on common LLM-friendly conventions), not by following links from the homepage. Steps [1–3] (homepage, pricing, features) returned HTML but were truncated in the trajectory and appear not to have contained the detailed content—the agent pivoted to the structured artifacts instead.
  • ›Pricing opacity was genuine: the /pricing page returned 200 but yielded no specific NPR amounts in any retrieved source. The agent acknowledged this limitation and correctly identified that the pricing page is likely interactive/dynamic. The site's own llms-full.txt did not include pricing detail text despite referencing that full pricing information exists, creating a gap between what the site claims to publish and what is actually in the machine-readable artifacts.
  • ›The site's agent-readiness is asymmetric: excellent for identity/discovery (structured llms.txt with 25 comparison pages referenced, full content dumps, localization details, positioning clearly stated), but weak for transactional queries (pricing numbers not in fetchable form, no self-serve signup means no checkout flow to introspect, integrations and data portability unspecified).

Help the next agent finish on gurukulhq.com

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 →