ora
stripedex.com
success
Claude Code · Haiku 4.51:05
intent

What does stripedex.com do and who is it for? Explain it back to me.

13steps
65.4sduration
$0.7256cost
149,261tokens
22 steps9 reasoning steps4 searches
home
docs
docs
/features
search
/hraness/stripedex
/hraness/stripedex/mai…
/data
search
search
home
search
/history/acquisitions
89%
on-site discovery
78%
reliability
56%
link following
path origin
  • previous resource56%
  • web search11%
  • prior knowledge33%
insight

The agent successfully understood stripedex.com by pivoting away from the heavily client-rendered homepage (which blocked content extraction) to the GitHub README, which provided a complete, structured definition of the project. The site itself was poorly navigable for an agent—most pages returned JavaScript-heavy HTML with no readable text—but the project's open-source nature made the true answer available via GitHub and search discovery. The agent then cross-referenced stripehistory.com to confirm the relationship and complete the picture.

  • Step [10] (GitHub README) was the primary content source and contained the core claim: 'an independent, open-source timeline of Stripe company history' with 200+ sourced events. This was the only step that returned machine-readable, semantically complete information about what stripedex does.
  • Steps [1], [3], [12], [17] (stripedex.com pages) all returned 200 HTTP but with only truncated HTML; the agent explicitly noted 'heavily JavaScript-rendered' and was unable to extract visible content. The site does not publish its value proposition, data structure, or functionality in a fetchable server-side form.
  • Step [18] (web search) surface stripehistory.com as an alternative/alias, and step [20] confirmed it uses the same stack (Next.js, same layout CSS). The agent had to use search and external discovery to validate relationships the site itself did not make clear.
  • Steps [4], [5] (direct guesses for /pricing, /features) returned 404s, confirming the site has a minimal URL structure and no dedicated pages for pricing or features—consistent with it being a free, open-source project, but leaving pricing information to be inferred rather than stated.
  • The agent never retrieved full page content from stripedex.com itself; the final answer was reconstructed entirely from the GitHub README (which explicitly claims stripedex.com is its web interface) plus search validation. This indicates the site is not agent-readable in its primary form and relies on an external reference to be understood.

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 →