Agent analytics for websites
ChatGPT, Claude, Perplexity and coding agents already read your site on behalf of the people behind them, and no browser pixel records it. Wake shows which agents come, what they try and where they stop, then tells you exactly what to change so agents can find, navigate and buy from you. Watching the agents is free for good; the changes and the insight are $100 a month after a 7-day trial with no card.
What Wake shows
- Who: the agent family (ChatGPT, Claude, Perplexity, Cursor, scripted clients), country and network, as a daily pseudonym.
- What: the pages they read, the API and MCP calls they make, the funnel from discovery to action.
- Where they stop: 401 walls, HTML error pages on machine paths, OAuth gates, docs dead ends, request loops.
- What to fix: file-level changes with evidence, and a weekly brief you can hand to a coding agent.
How it works
One file where the site is served: a Cloudflare Worker, Express middleware or Next.js middleware with the key inside. Agents never run JavaScript, so measurement happens at the server or the edge. Raw IP, user agent, paths, query strings, bodies, prompts, cookies and referrers are never stored.
Questions
- What is Wake?
- Wake is agent analytics for websites. It shows which AI agents (ChatGPT, Claude, Perplexity, Cursor, scripted clients) visit a site, what they try, where they stop, and what to change so they get through.
- How do AI agents drive revenue?
- People increasingly ask an assistant to research, compare and buy for them. The assistant visits your site as an agent. If it can find your docs, read your pricing, call your API or sign up, the person behind it becomes a customer; if it hits a wall, they never hear of you.
- Why can't Google Analytics or PostHog see AI agents?
- Agents fetch pages without running JavaScript, so a browser pixel never fires. Wake reads the request on the server or at the edge, where every agent visit is visible, and keeps only page, status, provider family and a daily pseudonym.
- How does Wake improve visibility and navigation for agents?
- It tells you exactly what blocks them: robots rules, missing llms.txt, HTML error pages on machine paths, OAuth gates with no instructions, API 401s with no next step. Each fix comes with the file-level change and a copyable brief for your coding agent.
- What does Wake store?
- Timestamp, method, page, status, provider family, country, an opaque daily nickname and behaviour signals. Never the IP address, user agent, query string, body, prompt, cookie or referrer.
- How do I install it and what does it cost?
- One file where the site is served: a Cloudflare Worker, Express middleware or Next.js middleware, with the key already inside. Watching the agents is free for good. The changes and the insight, where agents stop, what to fix, the weekly brief, are $100 a month after a 7-day trial with no card.
Read next