Get your site tolled

The whole job: a credits endpoint, a wallet per author, your origin. Start here.

The one read-only route on your domain that names who wrote each article and where their cut goes.

Optional: list your articles so AI buyers find them in the naulon directory before they’ve read one.

Publish what agents paid you, what they declined, and what people read free — and embed it as a badge on your own site.

PDFs, datasets and downloads are free until you pick them — and what tolling a paper costs you in Google Scholar.

How the money reaches you: buyer → author, direct, custody-free.

You were invited to claim your articles: accepting, setting the wallet your share lands in, and checking that it arrived.

Running an agent that reads tolled pages: one balance, agents with budgets, and what naulon can and cannot do with your money.

A signed POST (or a Slack/Discord/Teams message) when a settlement lands or an anomaly fires.

Per crawler: reads free, pays the toll, or refused outright, plus one-price section tolling.

The machine-readable licence we publish for your site, what it grants, and the one line for your robots.txt.

Cryptographically verified bot identity (Web Bot Auth), and masquerade attempts caught.

What the naulon fetcher is, how to recognize it (Web Bot Auth, signed as naulon.app), and how to allow or block it.

Two DNS records and a click: your own domain tollable through the edge, with a certificate issued and renewed for you.

If your origin has its own bot or rate protection: the header that lets naulon's traffic through, per platform, verified end to end.

When your origin’s edge rate-limits naulon: run the toll inside your own app, so the agent hits your origin directly. No shared IP, no 429.

The account-level bill, not the toll: when a period is actually invoiced, the two ways to pay one, and what an unpaid invoice does and does not cost you.

The two rosters around your account, what each role can actually do, and how an invite, a role change and a removal behave.

Single sign-on, data subject requests, reconciliation, the audit log, and scheduled exports and anomaly alerts — what each one does and who can configure it.

The HTTP API for pricing a resource, settling from your own runtime, and pulling earnings and audit data — plus the interactive reference served from the running code.

Mint an nln_live_ key, send it as a bearer token, and the scopes each endpoint needs.

The status codes and response shapes the API returns on failure.

The plan gate, the response row caps, and how to page through large results.