Agent analytics
See how agents use your API.
People and AI agents, across your docs site, MCP server, CLI and llms.txt. See who reads you, what they ask, and what they couldn't find.
readers people 1,240 · agents 3,815 by channel MCP 2,102 · llms.txt 911 · docs 1,240 · CLI 802 top agents Claude Code · Cursor · ChatGPT most read POST /v1/messages not found “bulk send limit” (41 searches) reported gaps 3 new from agents
What you see
Your API's real audience.
People vs agents
Every read and call, split by who made it: a person, an AI agent, a crawler or a script.
By channel
Docs site, markdown and llms.txt, MCP tools and CLI commands, side by side.
Which agents
Claude, ChatGPT, Cursor, Codex and more, plus the clients and models behind them.
Top questions
What people and agents search for, and which pages and endpoints answer them.
Missing answers
Searches and tool calls that came back empty: the docs you should write next.
Reported gaps
Agents using your MCP server report missing or wrong docs, grouped and de-duplicated, with the question that failed.
FAQ
Analytics questions.
How do you tell agents from people?
On the server, from each request's client and channel. Agents rarely run JavaScript, so browser-only analytics miss them.
Do you track my users personally?
No. Reports are aggregate. Visitor IDs are random and hold no personal data.
Can agents report problems with my docs?
Yes. Every hosted MCP server lets the agent report missing or wrong information straight to your inbox.