ora
openhandle.dev
success
Claude Code · Haiku 4.51:30
intent

What does openhandle.dev do and who is it for? Explain it back to me.

23steps
90.2sduration
$1.1538cost
355,828tokens
32 steps9 reasoning steps5 searches
home
search
docs
docs
docs
search
search
search
docs
/features
docs
docs
docs
docs
docs
search
sitemap
/compare
/use-cases
/apis
docs
/apis/instagram
docs
100%
on-site discovery
67%
reliability
67%
link following
path origin
  • previous resource67%
  • prior knowledge33%
insight

The agent partially satisfied the task by assembling a coherent explanation of OpenHandle's business model, target users, pricing, and platform coverage—but worked around a fundamentally inaccessible website. The site is a Next.js SPA that returns only boilerplate HTML and JavaScript bundles in fetches; all meaningful content is client-side rendered and invisible to the agent's text extraction. The agent recovered by discovering the sitemap (step [20]), which exposed the URL structure, then used prior knowledge and inferences from URL patterns to construct an answer. Critical details about differentiation, data freshness, rate limits, and exact platform maturity remain unknown.

  • Steps [23], [24], [26], [29], [30] all returned 200 status but contained only Next.js boilerplate HTML—no readable content. The agent could not extract text from any page fetch after the initial homepage.
  • The sitemap (step [20]) was the only structured, machine-readable artifact returned by the site. It exposed the URL hierarchy (/apis, /pricing, /compare, /use-cases, /changelog, /apis/{platform}) but not content. The agent used it as a discovery map, not a content source.
  • The agent inferred product details from prior knowledge (33% of the run's sources) and URL patterns rather than from page content. For example, it reasoned that /apis/instagram and /apis/tiktok pages likely contain platform-specific documentation, and that /compare contains competitive positioning—but never read those pages.
  • Critical gaps remain unfilled: the agent could not access the /compare page's actual comparison content, the /use-cases page details, or platform maturity/stability information. It flagged these as 'confusing' or 'missing' rather than unknown.
  • The agent's claim that OpenHandle supports 15+ platforms (Threads, YouTube, Reddit, Facebook, Snapchat, LinkedIn, Telegram, TikTok Shop, Google Ads) is not verifiable from the fetches shown; it appears to derive from prior knowledge or inferred from the sitemap's URL list, not from readable page content.

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 →