Resources · Content marketplaces · TollBit

TollBit charges AI bots at your door. FORA lets agents buy each page on your terms.

TollBit runs a paywall for AI bots on a subdomain of your site, and your CDN sends known AI bots there. FORA lets an AI agent buy each page under an offer your Exchange signs, and fetch it from your own CDN.

Updated

At a glance

TollBit and FORA, side by side

The facts a revenue team and an engineering lead act on.

TollBitFORA
Money
Who pays you, and when TollBit, through Stripe, early each month, in US dollars [1, 2]. Your Exchange operator, under its own terms. See About FORA.
Fees You keep your full rate. The buyer pays a fee on top; its size isn't published [3]. No Exchange fee at FORA's publisher console, beyond the payment system's. See About FORA.
What you see Daily bot analytics, and each sale: agent, page, price [3, 4]. Each sale in your operator's publisher console, with totals and a daily CSV. No bot-traffic report [26].
Contract A license between you and each buyer; TollBit isn't a party [5]. New York law [6]. No dispute call. Your agreement with your Exchange operator. Your terms go into each offer the Exchange signs [26, 27]. Disputes: see About FORA.
Status Live A publisher reports revenue [36]. No TollBit page names a big AI company as a buyer. Live See About FORA.
Your stack
DNS A TXT record, and an NS record that hands a subdomain to TollBit [7]. No record to add [26].
CDN One forwarding rule for 69 AI user agents [8]. Guides for 12 platforms [9]. A drop-in edge function. The rest depends on your own setup; FORA adds to what you run rather than replacing it.
Firewall and bot shield An allow rule for TollBit's fetcher in every layer [7]. On most CDNs they run first, so they must let signed requests and your two licensing files through. Keep them: the edge function knows AI agents mainly by the name they send [26, 28].
Your site and CMS No change. TollBit fetches, cleans and serves the page. Your HTTP logs, readers' requests included, go to TollBit [1, 4]. Serve one file, fora.json, from your site. The operator imports your pages from your sitemap [26].
Search traffic Googlebot and Bingbot aren't on TollBit's list; they reach your site as today [8]. Googlebot, Bingbot and Applebot always pass [28]. See Search traffic, below.
Upkeep On most platforms, update the bot list by hand each quarter [10]. Change your Exchanges by editing your FORA file, with nothing to redeploy [29].
Leaving No offboarding page. You can end the terms only with no active license [5]. Delete the edge function from your CDN.
The short answer

Bots that never asked, and agents that do

TollBit catches the bots that never asked.

Your CDN spots AI bots by the name they send and hands them to TollBit, which charges per page at your rate.

FORA serves the agents that do ask.

An agent signs each request, buys under a signed offer, and fetches with a signed link, which your CDN checks. You price by use, country, buyer type and unit.

Design
TollBit's rates behind a FORA Broker.

A Broker would call TollBit with each agent's own TollBit account and show TollBit's rates beside your FORA offers.

How you're paid

TollBit bills the buyer on delivery and pays you monthly

  1. You set rates per license, per 1,000 pages. Summarization covers "a summary, grounding, or citation with a single use license". Full Display lets a buyer "display the complete text of an article once". Custom is for a partner you have a deal with. Rates can differ by bot, page, keyword, time and directory (Setting rates).
  2. Buyers find you through TollBit and buy a pass for one URL. One API key searches TollBit's index, which covers sites "across the web" and flags TollBit's own. It shows each URL's licenses and prices (Licensed search, Rates).
  3. The pass is short-lived. TollBit calls it a token: "Tokens expire 5 minutes after issuance." Each works once and names the buyer's agent, the license type and the most the buyer will pay (Tokens).
  4. TollBit delivers the page. With a pass, TollBit fetches your page from your site, strips what you exclude, and returns Markdown or HTML (Security; Platform overview, §3.5).
  5. Billing waits for delivery. Nobody is billed "until the token is actually accepted and a 200 OK response is delivered" (Platform overview, §5.1).
  6. Your rate is your net. The buyer pays your rate plus "a small transaction fee on top of the rates you set" (Setting rates). TollBit doesn't publish the fee's size. You're paid through Stripe early each month, in US dollars (Platform overview, §1.4; Tokens).
The buyer asks TollBit for a pass for one URL; TollBit fetches your page and delivers it with 200 OK, and nobody is billed before that. The buyer then pays your rate plus TollBit's fee, whose size isn't published, and TollBit pays you your full rate monthly; the license is a contract between you and the buyer, and TollBit is not a party.
Where the money goes, and who signs the license. TollBit pays you; the license is between you and the buyer.
Text version

The buyer asks TollBit for a pass for one URL; TollBit fetches your page and delivers it with 200 OK, and nobody is billed before that. The buyer then pays your rate plus TollBit's fee, whose size isn't published, and TollBit pays you your full rate monthly; the license is a contract between you and the buyer, and TollBit is not a party.

TollBit in four numbers
1,000 pages
The unit you set each rate in, per license type [3]
5 minutes
How long a buyer's pass for one URL lasts. It works once [2]
Nearly 20%
Of TollBit's nearly 7,000 sites had earned money by April 2026. The CEO's figure, unaudited [37]
37 million
"content transactions" TollBit handled in Q2 2025, by its own count. It doesn't say how many were paid [13]
Who has been paid so far

Publishers report revenue. TollBit names no buyer.

[TNL Mediagene] has begun generating initial revenue from AI buyers.

TNL Mediagene, 15 brands on TollBit, December 2025, PR Newswire

TollBit counts sites that use it, whether or not they have rates switched on. The count rose from "over 200 publisher sites" in October 2024 (Series A) to the CEO's nearly 7,000 in April 2026. The homepage says "Trusted by over 10,000 sites" (vendor's figure, TollBit).

TollBit's 2024 funding post says it "has secured partnerships with the first AI companies", without naming them [14]. No TollBit page or release names OpenAI, Google, Microsoft, Meta, Amazon, Anthropic or Perplexity as a buyer.

What it takes on your site

Only bots on TollBit's list go to TollBit

Readers and search crawlers reach your site as today. The setup is five steps on your DNS, CDN and security layers, and nothing in your CMS.

Readers, search crawlers, unlisted bots and listed AI bots all reach your CDN, where a forwarding rule sends only the bots on TollBit's list to TollBit's Agent Site; that site gives a free copy (Open Access), blocks the bot, or by default answers 402 without a pass, and everything not on the list reaches your origin. TollBit's fetcher (tollbot/1.0) then pulls the page for a buyer with a pass through your CDN to your origin, and it gets through your WAF and bot shield only by an allow rule for TollBit's fetcher.
Who gets what when a request reaches your CDN.
Text version

Readers, search crawlers, unlisted bots and listed AI bots all reach your CDN, where a forwarding rule sends only the bots on TollBit's list to TollBit's Agent Site; that site gives a free copy (Open Access), blocks the bot, or by default answers 402 without a pass, and everything not on the list reaches your origin. TollBit's fetcher (tollbot/1.0) then pulls the page for a buyer with a pass through your CDN to your origin, and it gets through your WAF and bot shield only by an allow rule for TollBit's fetcher.

What can go wrong

What TollBit's own guides warn about

Where TollBit is ahead

What TollBit does that FORA doesn't

The differences, question by question

Eight questions a publisher asks of any licensing deal

TollBit is ahead on what you see; FORA on how you can price and on who can check a pass. The first three rows compare different jobs. Both license your pages to AI buyers, and they can share your CDN.

The questionTollBitFORA
How do you say what's for sale? Nowhere on your site. A forwarded bot gets a 402 by default; your rates live in TollBit's dashboard [3, 21]. Your fora.json names the Exchanges that sell your content, and you set terms with each [27].
How does a buyer find your content? TollBit's search, which covers sites across the web and flags its own network [11]. How the index is built isn't documented. From your file and your Exchange, or through a Broker [27, 31]. No index spans the network.
Who is the buyer, provably? Bots: by user agent, from a list of 69 [8]. Buyers: a TollBit account, bound into each pass, which only TollBit can check [1, 2, 4]. A signature on each request, checked against the buyer's published key [32]. The edge also matches the names bots send [28].
What lets a given use happen? A pass for one URL, five minutes, one use, checked by TollBit alone [2, 4]. A signed link that expires and can be bound to the agent's key. Any edge with the Exchange's public key can check it [27, 33].
Who sets the price, in what unit? You: per 1,000 pages, per license type, by bot, page, keyword, time and directory. US dollars [2, 3]. You: free, per unit (pages, text tokens, seconds or your own) or flat, limited by use, country and buyer type, with caps. A currency per price [27, 30].
How does money move? Through Stripe, monthly. You keep your full rate; the buyer pays an unpublished fee on top [1, 3]. Outside the protocol. See About FORA.
What do you see? Daily bot analytics, and each sale: agent, page, price [3, 4]. Each sale, in the publisher console your Exchange operator runs [26, 27]. No protocol call returns your sales.
What if the numbers are wrong? No dispute call, and no charge without a delivered page [1]. Then New York courts, or arbitration with TollBit [5, 6]. Defined in the protocol, handled under your operator's rules. See About FORA.
Running both

Both on one site today. TollBit's rates behind a Broker, as a design.

On one site Live

TollBit's docs ask "Can I use another AI marketplace like TollBit in parallel?" The answer: "Yes, this is dependent on how you set up your log exports and bot redirect policies" (Platform architecture). Order your CDN rules like this.

  1. FORA's buyers skip TollBit's rule. So do requests for your FORA file. TollBit's rule looks for the link's signature and expiry (Signed URL verification). FORA's edge function then checks the link and serves the page from your origin.
  2. TollBit's own fetcher goes to your origin. FORA's edge function refuses user agents with a word ending in "bot" on the paths you license, and tollbot/1.0 is one. Add it to the edge function's allow list, beside your search crawlers (FORA Server's edge configuration).
  3. Other AI bots get FORA's refusal or TollBit's paywall, path by path.
  4. Readers go to your origin.

On Cloudflare Enterprise, "Snippets execute earlier in Cloudflare's traffic sequence than Worker routes", so TollBit's rule runs first. On other plans "CloudFlare only runs one Worker per route", so your engineers combine TollBit's rule and FORA's edge function in one Worker (Cloudflare; Composition).

Behind a FORA Broker Design

A Broker would call TollBit's API with each agent's own TollBit account, never one of its own, as TollBit lets a platform act for a buyer (Platform overview, §4.3). An Exchange would sign each TollBit rate as a FORA offer, so the agent sees both offers and decides. How a Broker orders offers is on the hub.

Doesn't fit

Settling a FORA sale through TollBit. TollBit's API bills the calling account at TollBit's own rates, even for usage the buyer reports itself. It has no call that bills a price another Exchange set (Content).

Your CDN asks four questions in order: a request for your FORA file or with a FORA signed link skips TollBit's rule, and FORA's edge checks the link before your origin serves it; TollBit's fetcher goes to your origin; another AI bot gets FORA's refusal or TollBit's paywall, path by path; and readers go to your origin.
Both on one site: the order of your CDN rules. For your engineers.
Text version

Your CDN asks four questions in order: a request for your FORA file or with a FORA signed link skips TollBit's rule, and FORA's edge checks the link before your origin serves it; TollBit's fetcher goes to your origin; another AI bot gets FORA's refusal or TollBit's paywall, path by path; and readers go to your origin.

What to do

If you use TollBit, or are weighing it

  1. Ask what a buyer pays. You keep your full rate, and TollBit's fee on top isn't published. Ask for the total a buyer pays for a page at your rate. FORA itself is free, open-source software.
  2. Read the license you accept. Activating rates accepts TollBit's standard license, warranty included (Setting rates). Send the points below to legal.
  3. Count what you hand over. A subdomain under your name, and your HTTP logs, with your readers' requests in them. On most platforms your engineers also update the bot list by hand each quarter.
  4. Check your rule order. Let TollBit's fetcher through, and keep its rule off FORA links.
  5. Plan the exit. Remove the forwarding rule before the DNS records, or setups without a fallback show visitors errors.
  6. Ask about Web Bot Auth. TollBit logs the signature headers that some AI agents send with each request (Cloudflare). Ask whether it verifies them.
  7. Sell to agents as well. Name your FORA Exchanges in fora.json, with terms TollBit's rate card has no field for: a price by country or buyer type, or per text token (Rates).

Sources

Sources are checked on the date of publication.

TollBit

  1. Platform overview TollBit
  2. Tokens TollBit docs
  3. Setting rates TollBit docs
  4. Security TollBit docs
  5. Publisher Terms of Service TollBit
  6. Content License Agreement (standard license) TollBit
  7. Verifying a property TollBit docs
  8. Cloudflare TollBit docs
  9. Integrations TollBit docs
  10. Bot management TollBit docs
  11. Licensed search TollBit docs
  12. Rates TollBit docs
  13. TollBit and Akamai partnership TollBit blog
  14. Announcing our Series A TollBit blog
  15. TollBit homepage TollBit
  16. Static IPs TollBit
  17. Platform architecture TollBit docs
  18. Other platforms TollBit docs
  19. Configure Agent Site TollBit docs
  20. Content cache TollBit docs
  21. Default settings TollBit docs
  22. AWS (S3, CloudFront, ALB) TollBit docs
  23. Developer overview TollBit docs
  24. Enable analytics TollBit docs
  25. Content (API) TollBit docs

FORA

  1. Publisher onboarding FORA documentation
  2. What is FORA? FORA documentation
  3. Bot detection FORA documentation
  4. Edge function FORA documentation
  5. Licensing terms FORA documentation
  6. Broker FORA documentation
  7. Authentication FORA documentation
  8. Composition FORA documentation
  9. Signed URL verification FORA documentation
  10. FORA Server edge configuration FORA-Protocol on GitHub

Press, filings and others

  1. TNL Mediagene announces early success in AI content licensing PR Newswire
  2. The Washington Post's Arc XP adds TollBit Digiday

Set your own terms for AI agents

FORA is an open protocol and free, open-source software. Sell through any FORA marketplace, several of them, or your own: you set terms and a price per resource, and each Exchange signs your offers.

What is FORA? Run your own marketplace All content marketplaces Licensing terms