BeeToll
AI Crawler Toll Booth
AI bots read your content for free. Start charging rent.
Every day, crawlers from AI companies read your archive, and every day you get nothing for it. BeeToll identifies them, lets you decide which ones are welcome, and meters access for the ones you choose to charge — while human readers and search crawlers pass through untouched.
Who asked, and what happened
hindinews.example · last 30 days
- Human readers 1.24M never challenged
- Googlebot 84K exempt
- Bingbot 11K exempt
- GPTBot 18K metered
- ClaudeBot 9.4K metered
- PerplexityBot 6.1K blocked
Licensed access
early market
Metered and logged. What it earns depends on whether these companies choose to pay — nobody can quote you a figure for that yet.
humans · never challenged
search crawlers · exempt
structural · not a setting
llms.txt and robots.txt generated to match — stated policy = enforced policy
The problem
What this is costing you right now
Your server log is a list of people taking things
GPTBot, ClaudeBot, PerplexityBot and a dozen others work through your archive every day.
Your reporting, answered somewhere else
A reader asks an assistant a question your article answers.
Blocking everything is not a strategy either
A `Disallow: /` in robots.txt stops the scraping and earns you exactly as much as the scraping did.
How it works
What BeeToll actually does
No black box. Here is the whole mechanism, step by step.
BeeToll — how it works
-
1
Identify what is actually asking
A maintained registry of known AI crawlers, plus behavioural fingerprinting for the ones that disguise themselves, plus verification handshakes where a bot supports one. Human traffic is never part of this check.
-
2
You set a policy per bot
Research crawlers free if you want them to be. Commercial LLM crawlers charged. Anything you do not want, blocked. Different prices for your archive and your breaking coverage, because they are not worth the same.
-
3
Paying bots get metered access
A licensed path through the toll gateway with usage metered per crawler. Everything is logged, including what was accessed and when.
-
4
Non-payers get what you decided
Rate-limited or blocked — your rule, not ours. And your `llms.txt` and `robots.txt` are generated to match, so your stated policy and your enforced policy are the same thing.
-
5
You end up with an evidence trail
Per-crawler usage and earnings land in BeeScope, exportable. Even if a given company never pays, you now have documented proof of what they took — which is the starting position for any licensing conversation.
- Per-bot policy free, charged or blocked
- Search crawlers exempt by default, structural
- Humans never challenged no captcha, no gate
- Evidence trail what was taken, and when
In context
Where BeeToll sits on your page
GET /cricket/ind-vs-aus-report
User-Agent: GPTBot/1.2
no page rendered · no ads served · charged anyway
A crawler request never renders your page and never sees an ad slot. It takes the text and leaves — which is why it has to be charged at the door or not at all.
Your readers see the page exactly as they do today. Nothing about BeeToll touches human traffic.
Specifications
Full technical specification
Publishers compare specifications, not adjectives. Everything is here, including what depends on partners we do not control.
Detection & exemptions
| Crawler detection | A maintained registry of known AI crawlers, behavioural fingerprinting for user-agent maskers, and verification handshakes where a crawler supports one. Detection is a moving target and the registry is maintained work, not a one-time list. |
|---|---|
| Human traffic |
Never challenged, never rate-limited, never gated. Structural. A product that protects you from bots by inconveniencing your readers has taken more than it gave, and there is no configuration that turns this on.
|
| Search crawler exemption |
Googlebot, Bingbot and other search crawlers are exempt by default. Your search traffic is the thing paying your bills today; nothing here is worth risking it for. You can change this, but you have to do it deliberately.
|
Policy & declaration
| Policy engine | Per-bot rules — allow free, meter and charge, or block. Price rules per section so your archive and your breaking coverage can be valued differently. |
|---|---|
| Declared policy |
llms.txt and robots.txt generated and kept in sync with your actual enforcement, so what you publish and what you enforce never drift apart.
|
Gateway & ledger
| Gateway |
Metered licensed access over an HTTP 402-style flow, with a subdomain gateway option. CDN integration of the Cloudflare/Fastly class is roadmap — a stated intention, not a shipped capability.
|
|---|---|
| Logging | Tamper-evident access logs per crawler: what was requested, when, and under which policy. This is the part that has value even before anybody pays. |
| Ledger | Per-crawler usage and earnings in BeeScope, with an exportable evidence trail you can take into a licensing negotiation. |
Some capabilities depend on third-party approvals and platform policies that are not ours to promise. Where that is the case, the spec above says so explicitly.
Expected impact
What the industry reports
Every number below is an industry benchmark published by a third party. BeeOS has not shipped, so none of these are results we have produced.
Reported in published crawler-network data — an early market signal, not a settled benchmark benchmark 1
Moving fast in one direction. The share of your traffic that is machine rather than human is the number to watch.
Without BeeOS
- AI crawlers reading your archive
- Freely
- What you earn from them
- ₹0
- Record of what was taken
- None
- Human readers affected
- —
- Search traffic risk
- —
With BeeOS
- AI crawlers reading your archive
- On your terms
- What you earn from them
- Metered, where they pay
- Record of what was taken
- Exportable log
- Human readers affected
- Not at all
- Search traffic risk
- None — crawlers exempt
Expected difference
Scraped for free → licensed on your terms
No percentage here, because nobody can honestly quote one yet. What changes first is leverage: you go from having no position to having a metered, documented one.
~1 in 31
AI-bot visits per human visit, in published network data benchmark 1
An early market signal, not a benchmark — this ratio is moving fast.
Some pay
Publishers on toll networks already earning — from very little to meaningful benchmark 1
Reported spread is wide. Nobody can tell you where you would land.
Never
Times a human reader is challenged by this product
Structural. Search crawlers are exempt by default too.
Being straight with you: Here is the honest shape of this. The mechanism works — detection, metering and blocking are ordinary engineering. Whether it earns you anything depends on AI companies choosing to pay for access, and that is a young market where some pay, some negotiate and some ignore the toll entirely. What you get regardless is control and a documented record of what was taken. Anyone quoting you a confident monthly figure for this today is guessing.
Works with
Fits into the stack you already run
Platforms BeeOS integrates with — not customers, partners or endorsements.
- Google AdSense
- Google Ad Manager
- AdX (via partner)
- Prebid.js
- Amazon APS
- PubMatic
- Magnite
- Index Exchange
- Sharethrough
- Sovrn
Glyphs are generic shapes, not brand logos — these are platforms we integrate with, not endorsers.
Questions
BeeToll — frequently asked
Module 5 · AI-Era Monetization
The rest of the module
AI assistants read your work and send you no traffic. This module charges them for it, answers readers on your own site instead of somebody else's, and routes each session to whatever earns most from it.
BeeAnswer
On-Site AI Assistant
Readers ask ChatGPT. Let them ask you — and earn from every answer.
BeeRouter
Agentic Session Revenue Router
Stop optimizing pageviews. Start optimizing every visit.
BeeAudit
Free AI Revenue Leak Report
Before you trust us with your revenue, let us show you what you are losing.
Be first in line for BeeToll
BeeToll is under active development. Early-access publishers get priority onboarding, founder-level support on WhatsApp, and locked-in launch pricing.
No spam — we write only when something real ships.