ora
loops.so
success
Claude Code
intent

What does loops.so do and who is it for? Explain it back to me.

10steps
65.2sduration
$0.6090cost
111,111tokens
15 steps5 reasoning steps3 searches
home
docs
/features
docs
search
search
/loops-review
docs
docs
search
57%
on-site discovery
86%
reliability
29%
link following
path origin
  • previous resource29%
  • web search43%
  • prior knowledge29%
insight

The agent successfully gathered enough information to explain Loops' core function, pricing, target market, and competitive positioning, but had to work around an incomplete website by supplementing with third-party review sites. The site itself published core information (homepage, pricing page, about page) in fetchable form, but lacked a dedicated features page and detailed implementation docs accessible via direct navigation, forcing reliance on external sources for complete context.

  • ›Step [1] (homepage) provided meta descriptions stating Loops is 'email marketing software for SaaS teams' with event-driven capability and free plan basics, but the full marketing copy and feature breakdown were not extracted from the HTML response shown.
  • ›Step [3] (pricing page) returned pricing structure (contact-based, not send-based; free tier at 1,000 contacts; $49/month starter) in meta description, but the agent could not extract detailed tier breakdowns from the JavaScript-rendered page HTML and relied on third-party review sites [11] and [13] for complete pricing tiers.
  • ›Step [5] (about page) confirmed Y Combinator backing and team context via meta description, but did not surface customer names or use cases—those came from external reviews.
  • ›Step [11] (encharge.io review) and [13] (thatmarketingbuddy.com) were the primary content sources for pricing tiers, competitive comparison, and feature details, indicating the official Loops site did not publish this information in a machine-readable or easily accessible form.
  • ›Step [4] returned 404 for /features, forcing the agent to infer feature set from homepage copy and reviews rather than a dedicated feature page.
  • ›The site is Framer-based with JavaScript rendering; the agent could extract meta descriptions and basic structure but could not parse dynamically rendered pricing tables or detailed feature lists from the HTML snapshots provided.
  • ›The agent explicitly flagged gaps (missing features page, unclear event implementation, no detailed support tiers, no deliverability stats), showing it reached the limits of what the site's direct pages exposed.

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 →