ora
pillar.codes
success
Claude Code · Haiku 4.51:26
intent

What does pillar.codes do and who is it for? Explain it back to me.

19steps
86.4sduration
$1.4617cost
241,807tokens
22 steps3 reasoning steps11 searches
home
docs
/features
docs
search
/best/land-acquisition…
search
/p/266593/pillar
search
docs
search
/letters/automating-la…
search
search
search
search
search
search
search
62%
on-site discovery
63%
reliability
38%
link following
path origin
  • previous resource38%
  • web search38%
  • prior knowledge25%
insight

The agent successfully assembled a comprehensive explanation of pillar.codes by combining direct site fetches with supplementary web searches and external content. The site itself provided limited machine-readable detail—pricing page exists but lists no actual prices, and key navigation like /features and /blog returned 404s—forcing heavy reliance on third-party sources (founder interviews, YouTube demos, industry roundups) and prior knowledge to construct the answer. Despite these gaps, the agent delivered a coherent narrative covering what Pillar does, target audience, positioning, and honest callouts of information gaps.

  • The homepage [1] and about page [4] fetches returned valid 200 responses but appear to have been JavaScript-heavy Next.js apps that the agent could not fully parse for content; the agent relied on web search snippets and external interviews rather than site body text to extract core messaging.
  • The pricing page [2] returned 200 but contained no concrete dollar amounts—the agent correctly flagged this as a friction point ('you need to contact their sales team for quotes'), indicating the site deliberately hides pricing behind a paywall rather than publishing it.
  • Critical nav paths returned 404s (/features [3], /blog [9]), forcing the agent to infer feature lists from marketing materials, YouTube demos [19], and founder interviews [13] rather than official docs.
  • The agent sourced the differentiator claim (natural language/paragraph interface) from [13] (Dylan Goren's Thesis Driven essay), not from the site itself—this is a core value proposition that should live on pillar.codes but was only found through external thought leadership.
  • Web searches [6, 12, 14, 19] and external content [13] (Thesis Driven essay, YouTube demo) provided the bulk of structured information about features, use cases, and competitive positioning; the site's own fetches served mainly as entry points to confirm the domain and discover navigation paths.
  • The agent did not successfully extract pricing tiers or concrete competitor comparisons from the site; these gaps were acknowledged transparently in the final response rather than fabricated.

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 →