antistatique.com
success
Claude Code
intent

What does antistatique.com do and who is it for? Explain it back to me.

20steps
87.5sduration
$1.3071cost
214,148tokens
21 steps1 reasoning step10 searches
home
search
/en
/company/antistatique.…
search
/en/services/developpe…
/en/services/design
search
search
/en/services/drupal
search
search
search
/en/services
search
/organization/antistat…
search
/en/about
search
/en/portfolio
40%
on-site discovery
90%
reliability
20%
link following
path origin
  • previous resource20%
  • web search60%
  • prior knowledge20%
insight

The agent satisfied the task by assembling a comprehensive understanding of Antistatique from multiple site pages and external sources, though the site itself required heavy reliance on web search to piece together coherent positioning and the agent could not find pricing information anywhere. The site is moderately navigable but JavaScript-heavy and fragmented; core positioning and service details were distributed across individual service pages rather than consolidated in an overview, forcing the agent to synthesize information from separate fetches.

  • ›Step [2] (antistatique.net/en homepage) and step [3] (services page) provided high-level positioning (Swiss agency, marketing/branding/web solutions) but were insufficient alone to explain specialization or target clients. The agent needed step [16] (Drupal service page) to discover the critical differentiator: deep Drupal CMS specialization for enterprise projects.
  • ›Steps [12] (web development) and [13] (design/project management) returned service-specific pages but with limited client context or strategic positioning. Step [9] (about page) was fetched but returned only a JavaScript shell—actual content likely renders client-side, making programmatic extraction difficult.
  • ›Pricing information was completely absent from all fetched pages. The agent correctly flagged this as a finding ('CONFUSING/NOT FOUND') rather than inventing an answer, demonstrating appropriate uncertainty when faced with a blank surface.
  • ›The agent relied heavily on web search (steps [1], [4], [5], [8], [10], [14], [15], [18], [19]) to discover and validate information not directly readable from the site itself—particularly client names (Sotheby's, swisstopo), company founding date (2008), office locations, and team size. The site did not surface these details in a structured, easily harvestable format.
  • ›The site's Next.js architecture meant most HTML fetches contained only script tags and minimal static HTML content, forcing the agent to rely on metadata (title, description tags) and external sources rather than rendered page text. This made the site poorly agent-readable despite having good SEO metadata.

See every agent that visits antistatique.com

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 →