# Wake

> Wake shows a website which AI agents reach it, what they tried, where they got stuck, and what to change so agents can navigate the site, and the fixes that let the next agent get through. Raw IP, user-agent, query strings, bodies, cookies and referrers are never stored.

Wake has two halves that share one desk:

- **AXO** (agent experience optimization): a small collector on your edge or server mirrors agent requests, coarsened on your side, to Wake. The desk turns them into sessions, a funnel (discovered → read docs → authenticated → attempted action → converted), friction (auth walls, rejected calls, retry loops, docs dead ends) and ranked fixes with evidence. A session is *authenticated* only when a credential was accepted (a 2xx/3xx write on a sign-in path, or an account page after it), and *converted* only by a successful write on checkout; a 2xx API call is an attempted action. Crawlers are sessionised but never produce a docs dead end or a conversion gap. Detail: [What AXO measures](/wake/docs/axo).
- **AEO** (agent engine optimization): a readiness check of your public site as an agent sees it (homepage, robots.txt, llms.txt, sitemap, agent card), publish-ready discovery files (llms.txt, robots.txt, sitemap, agent card), and arrival counts judged by identified agents only. Crawlers are counted separately and never sold as agents. Generative engine optimization (GEO) is the related job of being quoted by an answer engine; the files overlap and the score does not. Detail: [AEO and GEO](/wake/docs/aeo).

## Where to go

| Need | Go to |
|---|---|
| Agent analytics, AXO, AEO, GEO, price, in one paragraph each | [Questions](/wake/docs/questions) |
| Why Google Analytics misses agents | [Analytics](/wake/docs/analytics) |
| What AXO measures | [AXO](/wake/docs/axo) |
| AEO, and how it differs from GEO | [AEO and GEO](/wake/docs/aeo) |
| llms.txt, robots.txt, sitemap, agent card | [Discovery files](/wake/docs/discovery) |
| Start with your website, no account | [/wake/start](/wake/start): deep scan, tasks and `wake-playbook.md` in one go; then "Verify my setup" once installed |
| Check any public site | `/wake/?host=yourdomain.com` |
| Open a desk for your site | [Start tracking](/wake/signup) |
| Install the collector | [Install](/wake/docs/install) |
| Read the data from code | [API](/wake/docs/api) · [OpenAPI](/api/wake/v1/openapi.json) |
| Ask your AI about your agents | [MCP](/wake/docs/mcp) (Claude Code, Cursor, Codex, Claude Desktop) |
| Terminal | [CLI](/wake/docs/cli) |
| What is kept | [Privacy](/wake/docs/privacy) · [Data processing addendum](/wake/docs/dpa) |
| What it costs | [Pricing](/wake/docs/pricing): watching is free for good; the changes and the insight are $100 a month after a 7-day trial, no card |
| The rules | [Terms](/wake/docs/terms) |

## The loop

1. **Verify** you own the host (DNS TXT or a well-known file).
2. **Deploy** the collector (Cloudflare Worker, Express middleware or Next.js middleware). Agents are headless, so a browser pixel never sees them; the collector does.
3. **Watch** the first agent session land. The desk, the API, the CLI and your AI assistant all read the same rows.
4. **Fix** what the friction says: a 401 with no instructions, a docs page with no runnable first request, a 5xx on the action call.
5. **List** the site: publish `llms.txt` (title, one blockquote summary, live links), allow the task agents in `robots.txt` (training crawlers are a separate choice), and judge arrivals by identified agents. The scan also checks what the fixes prescribe: a JSON error body on unknown paths, auth instructions on the API, a pricing page readable without JavaScript, Markdown twins of the docs.

## Vocabulary

- **Nickname**: a daily HMAC of the agent's network identity, computed on your side with your own secret. The same machine is a new nickname tomorrow; nothing in Wake can be joined back to an address.
- **Page class**: `home`, `docs`, `auth`, `pricing`, `checkout`, `account`, `search`, `api`, `discovery`, `other`. The collector sends the class, never the URL.
- **Friction kind**: `auth_wall`, `action_unauthorized` (401/403), `action_rejected` (400/422), `action_not_found` (404), `action_wrong_method` (405), `action_rate_limited` (429), `action_server_error` (5xx), `repeated_error` (the same method on the same page class failing three times with the same status; 404s on docs and discovery never count, they are probes), `abandoned_on_error`, `docs_dead_end`. Each kind maps to one remedy in the fixes.
- **Fix**: a friction kind with evidence. It needs three sessions, or a quarter of all sessions on a small site; severity reads both the count and the share (five sessions, or a quarter with at least three, is a block). Every fix carries `sessions`.
- **Identified agent**: a client that names itself (Claude, ChatGPT, Cursor, Perplexity…) or a user-triggered fetcher. Smithery scanners, Amazonbot, Meta, Yandex and bare Chrome on a crawler network are crawlers, reported but never billed.

This site is built with the same rules it recommends: a readable `llms.txt`, the full text in `llms-full.txt`, Markdown docs at `/wake/docs/*.md`, an agent card at `/.well-known/agent-card.json`, and an OpenAPI description.
