dhrv.pw
success
Claude Code
intent

What does dhrv.pw do and who is it for? Explain it back to me.

24steps
100.8sduration
$1.2244cost
479,225tokens
25 steps1 reasoning step9 searches
home
home
docs
/work
/services
docs
search
home
/lab
/contact
search
/0xdhrv
search
/0xdhrv
search
search
search
search
crafts.home
blog.home
search
/in/0xdhrv
search
/0xdhrv
47%
on-site discovery
47%
reliability
13%
link following
path origin
  • previous resource13%
  • web search53%
  • prior knowledge33%
insight

The agent assembled a coherent answer about dhrv.pw by relying almost entirely on web search results and external sources (GitHub, Behance, LinkedIn, Raycast profiles) rather than the site itself. The main dhrv.pw homepage returned only truncated client-side rendered HTML, making it unreadable; subsequent attempts to fetch common routes (/about, /work, /services, /pricing, /lab, /contact) all returned 404s. The agent successfully explained what Dhruv Suthar does (design engineer focused on minimalist web), who the site is for (employers/collaborators), pricing (not applicable—personal portfolio), and what's different (minimalist philosophy), but only by synthesizing fragments from external profiles and subdomains like crafts.dhrv.pw and blog.dhrv.pw, not from the main domain's own navigation or content.

  • ›The primary dhrv.pw domain is almost entirely inaccessible to machine reading: the homepage HTML is truncated client-side Next.js output, and all standard routes (/about, /services, /pricing, /work, /contact, /lab) return 404s, forcing the agent to rely on web search discovery and external platforms.
  • ›Web search results surfaced the site's tagline ('Design Engineer | Minimal Web Experiences') and revealed subdomains (crafts.dhrv.pw, blog.dhrv.pw, wiki.dhrv.pw) that were actually accessible, but these were not linked from or discoverable via the main domain itself.
  • ›The agent had to reconstruct Dhruv Suthar's professional identity from GitHub, LinkedIn, Raycast, Behance, and Codal employment records rather than from dhrv.pw's own content—the site functions as a brand placeholder rather than an information hub.
  • ›No pricing, services, or contact information exists on the site because it is a personal portfolio, not a commercial offering; the agent correctly inferred this but had no site-native way to confirm it (no /about or /services page to clarify intent).
  • ›The site's agent-readiness is very low: it offers no structured metadata (JSON-LD, OpenGraph details visible in truncated HTML are insufficient), no accessible navigation routes, and no content-bearing pages beyond subdomains the agent had to discover via search.

See every agent that visits dhrv.pw

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 →