stoj.multihead.dev
success
Claude Code
intent

What does stoj.multihead.dev do and who is it for? Explain it back to me.

3steps
30.0sduration
$0.0043cost
14,120tokens
4 steps1 reasoning step
home
docs
docs
100%
answer from your site
100%
answer efficiency
100%
followed site links
answer sources
  • from this site100%
url discovery
  • given in the task33%
  • followed a link67%
insight

Agent successfully gathered enough material to explain Støj's purpose, audience, pricing model, data sources, and API behavior. The site is moderately agent-ready: it publishes core facts in a fetched docs page and about page, but lacks comparison to alternatives, complete response schemas, terms of service, and detailed explanations of the estimation method—gaps the agent flagged honestly rather than filling from memory.

  • ›The site publishes pricing transparently on the About page ('no paid tier') and rate limits (60/min default) on the Docs page, making those sections straightforward to extract and cite.
  • ›Data accuracy claims are specific and well-sourced on the Docs page (Copenhagen: 2022 official map; elsewhere: 007-traffic-diff model with measured error: +1.3 dB bias, 4.8 dB MAE, 41% within ±3 dB on N=200 Copenhagen sample), giving the agent a factual basis for nuanced explanation.
  • ›The site does not compare itself to alternatives or name competitors; the agent correctly reported this absence rather than inferring differentiation from model memory.
  • ›Status codes and response semantics are explicitly documented in a table on the Docs page (distinguishing `unresolved` vs. `no_facade` vs. 502), removing ambiguity the homepage had left.
  • ›The agent did not fetch `/openapi.yaml`, `/llms.txt`, or `/SKILL.md`, relying instead on the three main pages; the response correctly notes these resources exist but were not fetched, avoiding false claims about their content.

See every agent that visits stoj.multihead.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 →