ora
lovable.dev
success
Claude Code
intent

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

10steps
55.7sduration
$0.7387cost
97,691tokens
13 steps3 reasoning steps4 searches
home
docs
docs
docs
/features
search
docs
search
search
search
83%
on-site discovery
33%
reliability
0%
link following
path origin
  • web search17%
  • prior knowledge83%
insight

The agent worked around an inaccessible homepage (403 Cloudflare challenge) to understand Lovable.dev by fetching the pricing page directly and relying heavily on web search results and third-party reviews. It successfully assembled a comprehensive answer about what Lovable does, who it's for, pricing, and competitive differentiation, but had to supplement with prior knowledge and external sources rather than drawing from the site's own documentation or homepage.

  • ›Step [2] (pricing page) was the only directly accessible, content-bearing fetch from Lovable's own domain; it returned structured pricing information but the response was truncated and didn't fully answer the 'what do they do' or 'how are they different' questions.
  • ›Steps [10] and [11] were third-party reviews and comparison guides (superblocks.com, layer3labs.io, innfactory.ai) that provided most of the substantive content about features, positioning, and competitive differentiation — the agent relied more on external aggregators than on Lovable's own site.
  • ›The homepage (step [1]) returned a 403 Cloudflare challenge, and /about, /docs, and /features all returned 404s, leaving Lovable's primary pitch and official documentation completely inaccessible; the agent had to infer positioning from pricing page and search results.
  • ›Web search (steps [7], [8], [9], [11]) was critical — 17% of sources came from web search vs. 83% prior knowledge, suggesting the agent leaned on its training data to fill gaps left by the site's limited accessibility.
  • ›The site does not appear to publish structured schema, comparison guides, or feature documentation in a directly-fetchable form; differentiation claims had to be extracted from third-party review sites.

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 →