The event meter
One number covers both halves of the product, so you are never choosing between measuring your website and measuring your agents. It counts rows actually written: an event that fails to store is not counted, and a replayed agent run does not count twice.
| This | Costs | Why |
|---|---|---|
| A pageview | 1 event | The tracker sends one beacon per view. |
| A visit that proves it is human | 1 event | On top of the pageview. A second beacon reports that the reader actually interacted, which is what separates a person from a crawler and what stops a one-page visit recording a duration of exactly zero. An engaged visit therefore costs two, and the free allowance was doubled when this was introduced so that nobody's effective ceiling fell. |
| A custom event or conversion | 1 event | A download, a checkout, a purchase: each is its own row. |
| An agent span | 1 event | One model call or one tool call. The billable unit on the agent side. |
| An agent run | 0 events | A run with no spans is a declaration, not a measurement, so it is free. |
| A filtered bot hit | 1 event | Bot traffic is stored and marked rather than dropped, so you can audit the filter. It is counted because it was written. |
| Reading your data | 0 events | The dashboard, the API and the MCP tools are all reads. Query as hard as you like. |
The counter resets on the first of the month, UTC.
Going over
The limit is a limit, not a surprise invoice. There is no overage billing: past the ceiling, further events are refused with a 429 naming the allowance the account has used up, so a redirect loop on someone else's site cannot generate a bill here, because there is no bill to generate.
An over-quota event is refused, never silently dropped. It returns that error and writes a loud server log line carrying the org, the site, the count used and the limit. A tracker that appears to work while recording nothing is indistinguishable from a bug, and you would go looking in entirely the wrong place.
Nothing already collected is touched. Going over stops new writes for the rest of the month. It does not hide your dashboard, revoke your keys, or delete a single row you already have.