Encypher vs TollBit
TollBit is a gate: its Bot Paywall authenticates, charges and blocks AI bot traffic routed through it. Encypher is a mark: a signed record in your content that stays in copies that keep it. They cover different ground.
Side by side
| TollBit | Encypher | |
|---|---|---|
| What it is | A paid, enforced access gate for AI bots | A signed mark inside the content |
| Where it works | On requests routed through the gate | In copies that keep the mark |
| Copies taken elsewhere | Outside the gate | Carry the mark, unless it was stripped or rewritten |
| Content scraped before | Outside the gate, if taken before it was set up | Covered, if it was signed first and kept the mark |
| Brings in revenue | Yes, from crawlers that pay | No. It carries proof and terms |
When to use each
- TollBit
- To control and charge AI bots that reach your site.
- Encypher
- To keep a signed record and terms in copies that leave your site, where the mark is kept.
- Both
- A controlled door for bot traffic, and a record in copies beyond it.
What TollBit does well
- One marketplace
- Publishers register once. AI companies license through one interface.
- Priced by use
- Publishers can price search, AI answers and training differently.
Where a gate stops
A gate controls requests that pass through it, which is stronger than a request in robots.txtrobots.txt: The file on a website that tells crawlers which pages they may fetch.. Copies taken from a syndication partner, a cache, or before the gate went up are outside it. A signed mark is in those copies when it was kept.
Using both
Open the gate
Route AI bot traffic through TollBit and set your prices.
Sign your work
Sign new articles and your archive with Encypher.
Check copies
When a copy turns up, check its mark. Send notice if you choose.
Create. Mark. Endure.
Keep your gate. Sign your content free so copies carry a record too.