pulkit.page
partial
Claude Code
intent

What does pulkit.page do and who is it for? Explain it back to me.

19steps
97.8sduration
$1.2759cost
407,505tokens
22 steps3 reasoning steps9 searches
home
docs
docs
search
search
/contact
/work
/projects
search
docs
/claude-directory
search
search
search
search
search
search
/pulkitxm/claude-direc…
/pulkitxm/claude-direc…
90%
on-site discovery
100%
reliability
40%
link following
path origin
  • previous resource40%
  • web search10%
  • prior knowledge50%
insight

The agent assembled a partial answer by relying heavily on GitHub documentation (claude-directory README) rather than content from pulkit.page itself. The website proved nearly opaque—all fetches returned truncated, JavaScript-rendered HTML that revealed no meaningful content. The agent compensated by inferring what pulkit.page *is* from external sources (GitHub repo, search results), but could not verify pricing, service offerings, or differentiation directly from the site, leaving several key questions unanswered.

  • ›Steps [1], [3], [4], [7], [8], [9], [11], [12] fetched pulkit.page routes but returned only boilerplate Next.js HTML headers, truncated at 4400 chars, with zero visible body content—the site is not crawlable by traditional content extraction.
  • ›Steps [19–20] (GitHub repo and README) were the only content-bearing sources. The agent extracted the entire answer from the claude-directory GitHub repository README and inferred that pulkit.page exists to showcase it, but never verified what pulkit.page's own homepage actually says.
  • ›The agent cited sources [pulkit.page, GitHub repo, pulkitxm.com] but the primary site itself contributed zero factual content to the final answer; prior knowledge (GitHub search results) and web search filled the gap.
  • ›Pricing was inferred as 'completely free' from the open-source license of the GitHub repo, not from any pulkit.page page declaring pricing or business model.
  • ›The agent explicitly flagged confusion points: /pricing and /work pages either don't exist or are inaccessible, no clear consulting/service offering, no biographical details about Pulkit, and navigation ambiguity—all stemming from the site's JavaScript-heavy, non-traversable structure.
  • ›The site is poorly agent-ready: it does not publish structured data, does not provide readable text in initial fetch, and does not expose navigation or content surface to HTTP-based crawlers. The agent had to rely on external GitHub documentation and prior knowledge to answer the task.

Help the next agent finish on pulkit.page

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 →