NanoTrans Edge · Decide
In developmentNot a wall, but a gateway where deals begin
NanoTrans Edge classifies AI bots in front of your site. Bots that want to buy get articles, bots that only take get a price, and disguised bots are stopped.
Bot classes
Four ways to handle a request
| Class | Examples | Handling |
|---|---|---|
| Humans and search engine bots | Browsers, search engine crawlers | Free pass. No effect on search traffic |
| Registered AI bots | AI crawlers from companies with an access plan | API key checked, access credit used, full article served |
| Unregistered AI bots | AI crawlers without an access agreement | HTTP 402 response with headline, preview, original link and registration details |
| Disguised scrapers | Spoofed user agents, abnormal request intervals | Rate-limited then blocked, evidence logged |
Your decisions
You set the policy yourself
Allow, charge or block per bot
Choose how each bot operator is handled and change it at any time. Every change records who made it and when.
Preview length
Decide how much of the headline and summary bots without an agreement can see.
Sales scope and exclusions
Choose which years and sections are for sale, and which articles to exclude.
Rollout
It starts with measurement
Measurement
The gateway runs in measurement mode only. Nothing is charged or blocked, and you see bot share, top bot operators and the most-taken articles.
Gateway on
Once you set your policy from the results, unregistered AI bots start receiving registration instructions.
Access plans and APIs
We sell access plans, news APIs and archive licenses to bot operators and data companies.
Settlement
You are paid for what is sold.
Publisher console
Settlement and transparency
You and NanoTrans read the same ledger
Terms set together
The revenue share and payment cycle are agreed with each publisher based on pilot results.
Append-only ledger
Every transaction is written to a ledger that cannot be edited, and you see the same ledger we do.