waveapp.dev
success
Claude Code
intent

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

2steps
19.6sduration
$0.0030cost
12,729tokens
3 steps1 reasoning step
home
llms.txt
100%
answer from your site
100%
answer efficiency
100%
followed site links
answer sources
  • from this site100%
url discovery
  • given in the task50%
  • followed a link50%
insight

The agent successfully read the homepage and llms.txt to explain WAVE's purpose, audience, and positioning. The site was reasonably navigable but lacked comprehensive pricing and documentation, forcing the agent to note gaps rather than fill them from memory.

  • ›The homepage and llms.txt were the only pages fetched; the agent did not explore features, calculator, or GitHub pages, limiting depth but confirming the core story was surface-available.
  • ›Pricing is genuinely absent from both fetched pages—no plans, tiers, or support model are stated, only a cost calculator tool and MIT licensing. The agent correctly reported this as unclear rather than inferring a business model.
  • ›The site positions WAVE explicitly (manual testing, cloud tools, code frameworks are the contrasts), but does not name specific competitors or publish a formal comparison, which the agent noted.
  • ›Alpha status is mentioned but undefined on the site (no reliability or support implications are explained), so the agent flagged this as confusing rather than guessing.
  • ›llms.txt was present and fetched (2xx), serving as an LLM-optimized summary that reinforced the homepage story without contradicting it, demonstrating basic machine-readability.

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