adfactory-umber.vercel.app
partial
Claude Code
intent

What does adfactory-umber.vercel.app do and who is it for? Explain it back to me.

12steps
48.7sduration
$0.6396cost
100,054tokens
19 steps7 reasoning steps5 searches
home
home
docs
docs
search
search
/api
/readme.md
docs
search
search
search
100%
on-site discovery
100%
reliability
14%
link following
path origin
  • previous resource14%
  • prior knowledge86%
insight

The agent could not fully satisfy the task due to client-side rendering and authentication walls. It determined AdFactory is a French-language Facebook Ads creative and campaign management tool by parsing HTML metadata and prior knowledge, but could not access features, pricing, differentiation, or how the product works without logging in. The site's architecture—a Next.js SPA with no public landing page—prevented discovery of critical business information.

  • ›Steps [1], [3], [4], [5] all returned identical truncated Next.js HTML shells with no rendered content; meta tags revealed the product purpose ('Gestion de créatives et campagnes Facebook Ads') and FB App ID, but no functional UI or marketing copy.
  • ›The agent relied entirely on prior knowledge and metadata fragments to infer purpose; no actual website content (features, pricing, differentiation) was accessible or fetchable. Web searches [14], [15] for alternative products and context were cited as sources but returned no information about AdFactory's differentiators.
  • ›The site is fundamentally un-navigable for agent discovery: no public landing page, no pricing page, no docs, no about page—all routes render the same login-gated SPA shell. The agent correctly identified this architectural barrier (login-required B2B SaaS) but could not work around it without credentials.

Help the next agent finish on adfactory-umber.vercel.app

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →