About this plugin
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
- Human traffic reads free. This is not a setting and there is no switch to change it.
- Titles, excerpts, your sitemap and your feeds stay free, because agents need to find you.
- Full article text is what carries a price.
- Nothing is ever charged with nowhere to send it. An article whose authors have no wallet anywhere, not on this site and not on the service it connects to, reads free.
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. 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.
External services
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.
app.
When it is contacted, and what is sent:
- When you connect or rotate a key, and hourly thereafter, to confirm the connection is live.
Sent: your API key and your site’s domain.
- When you verify ownership of your site. Sent: your API key and your site’s domain. The
service then fetches a challenge file or your homepage to confirm you control the domain.
- When an automated agent requests a full article and a price is needed. Sent: your API key,
the URL and slug of the requested article.
- When an agent pays. Sent: your API key, the article URL, the payment the agent signed, and
the wallet addresses credited on that article.
- When an administrator or editor approves an author’s request for a naulon payout account
(People screen). Sent: the author’s email address, the author’s id on this site
( wp-user- followed by their user number), and the email address of the person who
approved. naulon uses them to email the author an invitation. Nothing is sent for an author
who never asked, or whose request nobody approved.
What 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
app.
app/terms
app/privacy