fantastisch.mx
partial
Claude Code
intent

What does fantastisch.mx do and who is it for? Explain it back to me.

20steps
65.0sduration
$0.9132cost
303,674tokens
32 steps12 reasoning steps7 searches
home
/en
/en/work
/en/pricing
/de
/es
sitemap
/de/about
/de/contact
mcp-call
/de/contact
/de/portfolio
search
search
search
/bela-alvarez
search
search
search
search
92%
on-site discovery
54%
reliability
69%
link following
path origin
  • previous resource69%
  • web search8%
  • prior knowledge23%
insight

The agent gathered fragmented information about Fantastisch as a multidisciplinary artist collective specializing in paper sculpture, embroidery, and designer toys, but could not complete the task fully due to the site's poor navigation and absent business fundamentals. The homepage and language-specific pages (German, Spanish) returned valid responses but contained only truncated HTML with no usable content in the trajectory. The agent relied heavily on external Behance profile data and guesswork to assemble even partial answers; critical information on pricing, service scope, and portfolio examples remained inaccessible or obscured.

  • ›Steps [7, 8] (German and Spanish homepage fetches) returned 200 status but only showed language-redirect boilerplate HTML with truncations—no actual page content was captured. The site's routing logic dominated the response, leaving no discoverable content for the agent to extract.
  • ›Steps [11, 12] (About and Contact pages in German) similarly returned 200 but truncated, redirect-heavy HTML. The agent could not parse actionable service or pricing details from what was fetched.
  • ›Step [20] (Bela Álvarez Behance profile) was the only external, content-bearing source that provided solid identity/team information. The agent had to abandon the primary domain and resort to third-party portfolio platforms to answer 'who' and partially answer 'what they do.'
  • ›Pricing, portfolio, and business model remain completely absent from the fetched responses. The site provides no dedicated pricing page, no portfolio/work samples accessible via navigation, and no clear articulation of service offerings—forcing the agent to infer intent from medium names and guess at the business model.
  • ›The site's language routing mechanism (localStorage-based /de, /es, /en redirects) created navigation friction. Attempts to fetch /en/* paths returned 404s, and the agent could only access /de and /es root pages; neither returned substantive content within the fetch response body.
  • ›Site is poorly agent-ready: truncated HTML responses, no structured metadata (no JSON-LD, microdata, or schema.org markup visible in the fetches), no sitemap or index, no discoverable portfolio or pricing resources. The agent had to rely on 69% prior knowledge/artifact and external web search to construct any answer at all.

Help the next agent finish on fantastisch.mx

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 →