ora
superagent.sh
success
Claude Code
intent

What does superagent.sh do and who is it for? Explain it back to me.

26steps
117.2sduration
$0.4357cost
373,035tokens
40 steps14 reasoning steps14 searches
home
docs
docs
docs
search
docs
search
search
search
/guardrails
search
docs
search
/2025/12/29/superagent…
search
/superagent-ai/superag…
search
search
/companies/superagent
search
search
/superagent-lm
search
docs
search
search
33%
on-site discovery
67%
reliability
17%
link following
path origin
  • previous resource17%
  • web search67%
  • prior knowledge17%
insight

The agent partially satisfied the task by assembling a coherent explanation of Superagent's value proposition, target audience, and differentiation from external sources, but could not complete the pricing section due to broken website pages (404 errors on /pricing and /superagent-lm). The site's heavy reliance on client-side rendering and broken routing forced the agent to rely heavily on web search results and third-party documentation rather than primary sources, making it difficult to verify current pricing or confirm the exact commercial model.

  • ›The main website (superagent.sh) returned only HTML shells without rendered content; all substantive information came from external sources: Y Combinator company profile (step [29]), GitHub repository (step [24]), Help Net Security article (step [23]), and web search results pointing to third-party reviews.
  • ›The agent discovered core differentiators (SuperagentLM proprietary model, GitHub-native integration, open-source foundation) only through external reporting, not from superagent.sh itself. The site's own /pricing, /superagent-lm, and /guardrails pages returned 404 errors, making primary pricing and product details inaccessible.
  • ›The agent successfully reconstructed 'what they do' and 'who it's for' from external sources but explicitly flagged pricing as 'poorly documented' with only speculative token-based costs ($0.9–$1.9 per million tokens) sourced from third-party reviews rather than official documentation. This is a critical gap for a task that explicitly asked about pricing.
  • ›The site's reliance on JavaScript rendering without meaningful HTML metadata or structured data meant the agent could extract almost no information directly from superagent.sh fetches—all content-bearing steps are external sources that had already indexed and synthesized the company's positioning.

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 →