vacwork.app
partial
Claude Code
intent
What does vacwork.app do and who is it for? Explain it back to me.
17steps
79.3sduration
$1.2685cost
154,639tokens
27 steps10 reasoning steps10 searches
home
docs
docs
/faq
search
search
search
search
search
search
search
docs
/help
/how-it-works
search
search
search
100%
on-site discovery
14%
reliability
14%
link following
path origin
- previous resource14%
- prior knowledge86%
insight
The agent partially answered the task by extracting basic information from the homepage (what VacWork is, who it's for, key features), but could not find pricing details, competitive differentiation, or most other requested information because the site publishes only a minimal single-page app with no dedicated subpages, blog, FAQ, or help documentation. The agent filled gaps using prior knowledge and web searches that returned only the homepage URL repeatedly, indicating the site has minimal public-facing content.
- ›Step [1] (homepage fetch) was the only content-bearing resource; it returned the rendered HTML but the agent extracted only high-level metadata and feature lists—the actual page content was truncated in the response, limiting what could be gleaned.
- ›All attempted direct-guess URL probes ([3] /pricing, [4] /about, [5] /faq, [18] /blog, [19] /help, [20] /how-it-works) returned 404s or the homepage, indicating the site has no navigation structure or docs layers.
- ›Web searches ([7]–[16], [22]–[25]) consistently returned only the homepage URL with the tagline 'marketplace for piecemeal jobs & services'; no reviews, comparison content, pricing articles, or press coverage were indexed, suggesting the site is either very new or has minimal SEO surface.
- ›The agent could not answer critical task requirements (pricing model, how it differs from alternatives) and explicitly flagged these as missing rather than inferring them—showing appropriate transparency about site-provided vs. assumed information.
- ›The site appears to be a Next.js single-page app (evidenced by metadata references and 404 handling) with no public-facing blog, help center, or subpages, making it opaque to discovery-layer navigation.
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 →