AI agents read your work to answer questions. They do not click your ads, they do not subscribe, and they rarely send a reader back. naulon prices that read.
A human visitor is never affected. They see exactly what they always saw, at the same speed. An automated agent asking for the full text of an article gets a price instead, pays it, and then reads. What it pays goes to the people credited on that article, straight to their wallets, with nothing pooled or held in between.
How it decides
What you configure
You paste one key, click verify, and choose what is tolled. Your authors each add their own wallet address from their normal WordPress profile. An author never sees anyone else’s earnings, and only editors and administrators can see the site’s total.
How you know it is working
The Setup screen has a Test toll button that asks your own site for one of your articles while presenting a crawler’s user agent, over real HTTP, and shows you what came back: the status, the price, the chain, and the wallet being paid. Diagnostics runs the same check against caching, lists the last decisions the toll made (machine requests only, since readers are never logged) and says plainly when something between the internet and WordPress is answering from a cache.
Where the money goes
Payment is direct: the agent pays your authors. Each payment settles to the author’s own Circle Gateway balance for the wallet address on their profile, and only that wallet can withdraw it, at https://naulon.app/earnings, with no naulon account needed. This plugin never takes custody of funds, never holds a balance, and never asks you to top anything up. There is no wallet on this site holding money.
Self-hosting
The whole protocol is open source. The connectivity field takes either a hosted key or the URL of a gate you run yourself, and everything else works identically.
This plugin relies on an external service to price a read and to settle a payment, because
settlement cannot be performed inside WordPress. Nothing is contacted until you enter a key.
Entering it is the consent, and until then the plugin makes no outbound requests at all,
not one, to anywhere.
Service: naulon (https://naulon.app), reached at https://gate.naulon.app.
When it is contacted, and what is sent:
wp-user- followed by their user number), and the email address of the person whoWhat is never sent: your article content, your readers, your visitor logs, and anything
about human traffic. Human requests never contact the service at all.
The plugin adds a suggested paragraph to Settings Privacy that says all of this, for your own
privacy policy.
If you point the connectivity field at your own self-hosted gate instead of a key, the plugin
talks only to that server and never to naulon.app.
Terms of service: https://naulon.app/terms
Privacy policy: https://naulon.app/privacy