sibbl.net
success
Claude Code
intent

What does sibbl.net do and who is it for? Explain it back to me.

17steps
57.6sduration
$0.5660cost
66,966tokens
23 steps6 reasoning steps5 searches
home
/services
docs
docs
/products
search
search
changedetection.home
home
/app
docs
/projects
search
/sibbl/wohnung-scraper
search
search
/sibbl/wohnung-scraper…
75%
on-site discovery
25%
reliability
33%
link following
path origin
  • previous resource33%
  • web search25%
  • prior knowledge42%
insight

The agent successfully completed the task by assembling a coherent explanation of sibbl.net, but had to work around a nearly empty primary site. The homepage ([1]) only revealed Sebastian Schubotz's personal portfolio with no service information; the agent discovered the actual project (Wohnung Scraper) through web search and GitHub ([17], [20]), not from the domain itself. The site is not agent-ready for discovery — sibbl.net publishes no details about its projects, pricing, or differentiators directly.

  • ›Step [1] (homepage) returned only a personal portfolio page with minimal metadata; it contained no service description, pricing, features, or project links. All substantive information came from external sources.
  • ›Steps [17] and [20] (GitHub repository and README) were the only content-bearing sources for the actual product information (Wohnung Scraper features, open-source model, self-hosting requirement, supported providers, and limitations). The agent discovered these via web search [16], [18], [20] — not via navigation from sibbl.net.
  • ›The site failed to surface any project documentation, hosted demo, or explanation directly at sibbl.net. All navigation tests ([3], [4], [5], [6], [14], [15]) returned 404s. The agent had to use prior knowledge (recognizing common paths like /services, /pricing, /blog) and external search to piece together what sibbl.net does.
  • ›Pricing information was absent from both the site and GitHub docs — the agent correctly identified it as free and open-source only by reading the GitHub project structure and README, which made no mention of commercial offerings.
  • ›The site's identity layer ("what does this do?") is opaque to automated discovery: no llms.txt, no structured data, no project description on the homepage, and all external-facing documentation lives on GitHub rather than being mirrored or linked from the primary domain.

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 →