Your public toll record
Your dashboard already shows which agents came, which of them paid, and which walked away at your price. All of that is private. The toll record is the same data, aggregated, on a page anyone can open — and a badge you can put on your own site so readers see it without going anywhere.
It is off until you turn it on, and turning it off takes it down again.
What gets published
Your directory page at /directory/your-site.example grows a panel carrying:
- what agents paid you over the last 90 days,
- how many paid, how many saw the price and left, and what those would have paid,
- how many reads were served for nothing — people, and any crawler you allow-listed,
- the agents that came, by name, with those same three counts each.
An agent that signed its requests (Web Bot Auth) appears under its verified identity and is marked as verified. An unsigned crawler we recognise appears under its registry name — GPTBot, ClaudeBot, and so on.
Anything we cannot name is counted under other agents, never under the string it sent. A user agent is free text the caller chooses, and bespoke crawlers routinely put a contact address in theirs; publishing it would put a third party's details on a page anyone can read. You still see all of that traffic on your own audit page, where the raw string is the only identity such a client has.
What does not
Counts and totals only. The record carries no article, no URL, no slug, no visitor, no timestamp of any individual request, and no wallet address. Nothing in it can be turned back into a single read. Your payout address is a separate switch — see Show your payout address in the same panel — and stays private unless you turn that one on too.
If your site is busy enough that the record counts more requests than it reads in one pass, the panel says so and prints the number it counted from. It will not quietly show you a fraction of your own traffic as if it were the whole.
The window is fixed at 90 days for everyone. There is no way to pick a flattering month, which is the point: a record you could tune is not evidence.
Turning it on
Dashboard → your site → Discovery → Publish your toll record.
Two things must be true for the page to serve it: the site is listed in the directory, and this switch is on. Turn either one off and the record disappears within five minutes, along with the badge.
If your site has no traffic yet, the panel does not appear at all. An empty record reads as a broken toll rather than a new one.
The badge
The panel gives you a snippet to copy. It looks like this:
[](https://naulon.app/directory/your-site.example)Or as HTML:
<a href="https://naulon.app/directory/your-site.example">
<img src="https://naulon.app/api/badge/your-site.example.svg" alt="naulon">
</a>The image is a self-contained SVG — no script, no external font, no cookie. It carries your earned total and your paid-read count, it refreshes about every five minutes, and it links back to the full record.
It always renders. If your record is off, or the host is one we do not serve, the badge draws itself as no record rather than breaking into an empty image box on your page.
Freshness
Both the page and the badge are cached for five minutes. A read that settles now shows up on the next refresh, not instantly. That cache is what makes the badge safe to embed on a high-traffic page.
Turning it off
Same switch. The next request for the page and the next refresh of the badge stop serving the record; the badge falls back to no record. Nothing is retained on the public side — the panel reads your live traffic each time, so there is no published copy left behind.