What does spoorkaart.zaza.dev do and who is it for? Explain it back to me.
- previous resource22%
- web search44%
- prior knowledge33%
The agent partially satisfied the task by assembling a coherent explanation of spoorkaart from web search results and external sources, but the primary site itself (spoorkaart.zaza.dev) was functionally opaque—it returned only a rendered Next.js app with no visible text, documentation, or interactive content in the fetched HTML. The agent compensated by using search snippets, the creator's portfolio, and a blog post about Dutch train maps to infer what the product does. The site itself is not agent-navigable; understanding it required external sources and prior knowledge.
- ›Step [1] (homepage fetch) and steps [3–5] (attempt to reach /about, /pricing, /faq) all returned truncated Next.js HTML with no readable content—the site is a client-rendered React app that provides no server-side text, metadata, or structured data for discovery. The agent had to rely entirely on web search and external sources.
- ›Step [8] web search returned the homepage title 'I Love Trains' and a snippet mentioning 'customizable map simulating every Dutch train that ran on a real day'—this became the primary source of the core explanation. The search result snippet, not the site itself, contained the actionable information.
- ›Steps [10] and [17] (creator's portfolio and GitHub profile) were visited but also returned only truncated HTML, providing no additional clarification about pricing, features, or how to use the product. The creator's own site offered no public-facing documentation.
- ›Step [27] (blog post from 2018 about 'A Slightly Better Spoorkaart') provided historical context about Dutch train maps but did not explain spoorkaart.zaza.dev specifically, revealing that the site deliberately publishes minimal information.
- ›The agent correctly identified that pricing information is absent and the product appears free, but stated this as an inference rather than from documented policy—no payment layer exists on the site.
- ›The agent had to explicitly call out multiple missing features (no about page, no help text, no feature guide, unclear day-selection mechanism, no linked GitHub repo) because the site provides no answers to these common discovery questions.
Help the next agent finish on spoorkaart.zaza.dev
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 →