From a8a711e05352b9affc41b7b7bc5f5c3ada5b2c71 Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Wed, 11 Mar 2026 14:58:43 +0000 Subject: [PATCH 01/11] Create doc `how-monetization-works` --- docs/Publishers/_order.yaml | 1 + docs/Publishers/how-monetization-works.md | 7 +++++++ 2 files changed, 8 insertions(+) create mode 100644 docs/Publishers/how-monetization-works.md diff --git a/docs/Publishers/_order.yaml b/docs/Publishers/_order.yaml index ede1715..5b13f3c 100644 --- a/docs/Publishers/_order.yaml +++ b/docs/Publishers/_order.yaml @@ -5,3 +5,4 @@ - other-access-methods - admin - faqs +- how-monetization-works diff --git a/docs/Publishers/how-monetization-works.md b/docs/Publishers/how-monetization-works.md new file mode 100644 index 0000000..85386c9 --- /dev/null +++ b/docs/Publishers/how-monetization-works.md @@ -0,0 +1,7 @@ +--- +title: How Monetization Works +deprecated: false +hidden: false +metadata: + robots: index +--- \ No newline at end of file From 2be2dffb220cc3f22d20ccc558b3a75d48c59e9b Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Wed, 11 Mar 2026 14:58:54 +0000 Subject: [PATCH 02/11] Reorder doc `how-monetization-works` --- docs/Publishers/_order.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Publishers/_order.yaml b/docs/Publishers/_order.yaml index 5b13f3c..78a7355 100644 --- a/docs/Publishers/_order.yaml +++ b/docs/Publishers/_order.yaml @@ -2,7 +2,7 @@ - properties - integrations - marketplace +- how-monetization-works - other-access-methods - admin - faqs -- how-monetization-works From b1960c1ab5ba440d046b8bb5552c06881c1feede Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Wed, 11 Mar 2026 20:48:05 +0000 Subject: [PATCH 03/11] Update doc `how-monetization-works` --- docs/Publishers/how-monetization-works.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/Publishers/how-monetization-works.md b/docs/Publishers/how-monetization-works.md index 85386c9..8be9ecc 100644 --- a/docs/Publishers/how-monetization-works.md +++ b/docs/Publishers/how-monetization-works.md @@ -4,4 +4,9 @@ deprecated: false hidden: false metadata: robots: index ---- \ No newline at end of file +--- +# Content Intent + +TollBit allows developers to specify their intent when retrieving content, and will be able to serve different types of data with different monetization flows, for each of these intents. These can range from indexing content for building an internal knowledge graph, fetching static content in Markdown for RAG to respond to a user query, or getting a simplified version of the site that preserves key structure to enable faster agentic browsing. + +
From cbe0f86ec166cbd8435396fbd24d1f698f0cce45 Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Fri, 13 Mar 2026 21:31:13 +0000 Subject: [PATCH 04/11] Update doc `how-monetization-works` --- docs/Publishers/how-monetization-works.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/docs/Publishers/how-monetization-works.md b/docs/Publishers/how-monetization-works.md index 8be9ecc..2967006 100644 --- a/docs/Publishers/how-monetization-works.md +++ b/docs/Publishers/how-monetization-works.md @@ -5,7 +5,23 @@ hidden: false metadata: robots: index --- -# Content Intent +We want to provide a high level walkthrough of how a developer accesses your content, and how TollBit ensures that this access is secure and tracked to ensure you are fairly compensated. + +### Agent Registration + +When a developer first signs up, they are required to register their user agent to the TollBit Platform. TollBit maintains this global registry of all user agents on the platform, and verifies their identity and connects them to the developer accounts. + +### Requesting Access + +Developers are able to see who is on the TollBit marketplace and which of them are ready to transaction. However, do not initially have any visibility into their rates or licenses. They must request access to publishers through the developer portal, and TollBit will vet each developer before granting them access. + +### Tokens + +Tokens are one-time access grants tied to specific pages and user agents. The token system allows authenticated access for retrieving content, with a one-time use model to ensure security. + +Tollbit tokens are [JWTs](https://datatracker.ietf.org/doc/html/rfc7519) used to authorize a specific content request. They include authentication details, request intent, and, when applicable, pricing and license terms. Tollbit generates and validates tokens automatically; this section explains the token claims for reference. Tokens expire 5 minutes after issuance. + +### Content Intent TollBit allows developers to specify their intent when retrieving content, and will be able to serve different types of data with different monetization flows, for each of these intents. These can range from indexing content for building an internal knowledge graph, fetching static content in Markdown for RAG to respond to a user query, or getting a simplified version of the site that preserves key structure to enable faster agentic browsing. From 12a69d54b96d9add10de3a942f708b574ce6aa99 Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Fri, 13 Mar 2026 22:33:31 +0000 Subject: [PATCH 05/11] Move doc `how-monetization-works` under `faqs` --- docs/Publishers/_order.yaml | 1 - docs/Publishers/faqs/_order.yaml | 2 +- docs/Publishers/{ => faqs}/how-monetization-works.md | 0 3 files changed, 1 insertion(+), 2 deletions(-) rename docs/Publishers/{ => faqs}/how-monetization-works.md (100%) diff --git a/docs/Publishers/_order.yaml b/docs/Publishers/_order.yaml index 78a7355..ede1715 100644 --- a/docs/Publishers/_order.yaml +++ b/docs/Publishers/_order.yaml @@ -2,7 +2,6 @@ - properties - integrations - marketplace -- how-monetization-works - other-access-methods - admin - faqs diff --git a/docs/Publishers/faqs/_order.yaml b/docs/Publishers/faqs/_order.yaml index 6a121f2..0a6829d 100644 --- a/docs/Publishers/faqs/_order.yaml +++ b/docs/Publishers/faqs/_order.yaml @@ -1,7 +1,7 @@ - index.md - platform-architecture.md - bot-management.md +- how-monetization-works - monetization.md - security.md - pricing.md - diff --git a/docs/Publishers/how-monetization-works.md b/docs/Publishers/faqs/how-monetization-works.md similarity index 100% rename from docs/Publishers/how-monetization-works.md rename to docs/Publishers/faqs/how-monetization-works.md From 72bbb2c334b182f573bf835ddf70755c9e714ea4 Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Fri, 13 Mar 2026 22:33:36 +0000 Subject: [PATCH 06/11] Move doc `how-monetization-works` into `Publishers` --- docs/Publishers/_order.yaml | 1 + docs/Publishers/faqs/_order.yaml | 1 - docs/Publishers/{faqs => }/how-monetization-works.md | 0 3 files changed, 1 insertion(+), 1 deletion(-) rename docs/Publishers/{faqs => }/how-monetization-works.md (100%) diff --git a/docs/Publishers/_order.yaml b/docs/Publishers/_order.yaml index ede1715..5296462 100644 --- a/docs/Publishers/_order.yaml +++ b/docs/Publishers/_order.yaml @@ -1,6 +1,7 @@ - a-tollbooth-for-your-content - properties - integrations +- how-monetization-works - marketplace - other-access-methods - admin diff --git a/docs/Publishers/faqs/_order.yaml b/docs/Publishers/faqs/_order.yaml index 0a6829d..3fc5084 100644 --- a/docs/Publishers/faqs/_order.yaml +++ b/docs/Publishers/faqs/_order.yaml @@ -1,7 +1,6 @@ - index.md - platform-architecture.md - bot-management.md -- how-monetization-works - monetization.md - security.md - pricing.md diff --git a/docs/Publishers/faqs/how-monetization-works.md b/docs/Publishers/how-monetization-works.md similarity index 100% rename from docs/Publishers/faqs/how-monetization-works.md rename to docs/Publishers/how-monetization-works.md From 0206208b81584561a172900f975edb64c3565552 Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Fri, 13 Mar 2026 22:39:55 +0000 Subject: [PATCH 07/11] Update doc `how-monetization-works` --- docs/Publishers/how-monetization-works.md | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/docs/Publishers/how-monetization-works.md b/docs/Publishers/how-monetization-works.md index 2967006..0b47520 100644 --- a/docs/Publishers/how-monetization-works.md +++ b/docs/Publishers/how-monetization-works.md @@ -1,11 +1,19 @@ --- -title: How Monetization Works +title: TollBit Agent Site deprecated: false hidden: false metadata: robots: index --- -We want to provide a high level walkthrough of how a developer accesses your content, and how TollBit ensures that this access is secure and tracked to ensure you are fairly compensated. +Your Agent Site, which is automatically set up after you onboard to TollBit, is how you control how the agentic internet sees your content. We want to provide a high level walkthrough of how agents access your content and the different layers of controls you can provide. + +## Whitelisting Bots + +By default, your agent site blocks all bot access. However, there are many circumstances in which you wish to allow certain bots to be able to access your content. The TollBit Agent Site allows you to whitelist specific bots to be able to retrieve your content in Markdown. + +## Monetization + +Monetization is an additional layer of access controls you can provision over your Agent Site. This enforces that all agents that wish you access your content go through the follow workflow. ### Agent Registration @@ -15,7 +23,9 @@ When a developer first signs up, they are required to register their user agent Developers are able to see who is on the TollBit marketplace and which of them are ready to transaction. However, do not initially have any visibility into their rates or licenses. They must request access to publishers through the developer portal, and TollBit will vet each developer before granting them access. -### Tokens +### Token Generation + +In order to access content, developers must generate TollBit Tokens to include with each of their requests to your agent site. Tokens are one-time access grants tied to specific pages and user agents. The token system allows authenticated access for retrieving content, with a one-time use model to ensure security. @@ -25,4 +35,6 @@ Tollbit tokens are [JWTs](https://datatracker.ietf.org/doc/html/rfc7519) used to TollBit allows developers to specify their intent when retrieving content, and will be able to serve different types of data with different monetization flows, for each of these intents. These can range from indexing content for building an internal knowledge graph, fetching static content in Markdown for RAG to respond to a user query, or getting a simplified version of the site that preserves key structure to enable faster agentic browsing. -
+### Transactions + +Each request is ledgered as a transaction within our system, and all transactions include data around who, what and when it was accessed, the value of the transaction, the license it was retrieved under, and additional metadata that developers pass back, including information about the queries that led to retrieving that content. You are paid out at the end of each month for your total usage across all developers during the previous month. From 52ac5ac457eea3ae44df754b95f8f7305b4a9fc8 Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Fri, 13 Mar 2026 22:44:05 +0000 Subject: [PATCH 08/11] Delete doc `how-monetization-works` --- docs/Publishers/_order.yaml | 1 - docs/Publishers/how-monetization-works.md | 40 ----------------------- 2 files changed, 41 deletions(-) delete mode 100644 docs/Publishers/how-monetization-works.md diff --git a/docs/Publishers/_order.yaml b/docs/Publishers/_order.yaml index 5296462..ede1715 100644 --- a/docs/Publishers/_order.yaml +++ b/docs/Publishers/_order.yaml @@ -1,7 +1,6 @@ - a-tollbooth-for-your-content - properties - integrations -- how-monetization-works - marketplace - other-access-methods - admin diff --git a/docs/Publishers/how-monetization-works.md b/docs/Publishers/how-monetization-works.md deleted file mode 100644 index 0b47520..0000000 --- a/docs/Publishers/how-monetization-works.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: TollBit Agent Site -deprecated: false -hidden: false -metadata: - robots: index ---- -Your Agent Site, which is automatically set up after you onboard to TollBit, is how you control how the agentic internet sees your content. We want to provide a high level walkthrough of how agents access your content and the different layers of controls you can provide. - -## Whitelisting Bots - -By default, your agent site blocks all bot access. However, there are many circumstances in which you wish to allow certain bots to be able to access your content. The TollBit Agent Site allows you to whitelist specific bots to be able to retrieve your content in Markdown. - -## Monetization - -Monetization is an additional layer of access controls you can provision over your Agent Site. This enforces that all agents that wish you access your content go through the follow workflow. - -### Agent Registration - -When a developer first signs up, they are required to register their user agent to the TollBit Platform. TollBit maintains this global registry of all user agents on the platform, and verifies their identity and connects them to the developer accounts. - -### Requesting Access - -Developers are able to see who is on the TollBit marketplace and which of them are ready to transaction. However, do not initially have any visibility into their rates or licenses. They must request access to publishers through the developer portal, and TollBit will vet each developer before granting them access. - -### Token Generation - -In order to access content, developers must generate TollBit Tokens to include with each of their requests to your agent site. - -Tokens are one-time access grants tied to specific pages and user agents. The token system allows authenticated access for retrieving content, with a one-time use model to ensure security. - -Tollbit tokens are [JWTs](https://datatracker.ietf.org/doc/html/rfc7519) used to authorize a specific content request. They include authentication details, request intent, and, when applicable, pricing and license terms. Tollbit generates and validates tokens automatically; this section explains the token claims for reference. Tokens expire 5 minutes after issuance. - -### Content Intent - -TollBit allows developers to specify their intent when retrieving content, and will be able to serve different types of data with different monetization flows, for each of these intents. These can range from indexing content for building an internal knowledge graph, fetching static content in Markdown for RAG to respond to a user query, or getting a simplified version of the site that preserves key structure to enable faster agentic browsing. - -### Transactions - -Each request is ledgered as a transaction within our system, and all transactions include data around who, what and when it was accessed, the value of the transaction, the license it was retrieved under, and additional metadata that developers pass back, including information about the queries that led to retrieving that content. You are paid out at the end of each month for your total usage across all developers during the previous month. From 588bc04900edcd2470dacc55cfac2cb554b32a36 Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Fri, 13 Mar 2026 22:44:31 +0000 Subject: [PATCH 09/11] Create doc `agent-site` --- docs/Publishers/_order.yaml | 1 + docs/Publishers/agent-site.md | 40 +++++++++++++++++++++++++++++++++++ 2 files changed, 41 insertions(+) create mode 100644 docs/Publishers/agent-site.md diff --git a/docs/Publishers/_order.yaml b/docs/Publishers/_order.yaml index ede1715..ee47f9d 100644 --- a/docs/Publishers/_order.yaml +++ b/docs/Publishers/_order.yaml @@ -5,3 +5,4 @@ - other-access-methods - admin - faqs +- agent-site diff --git a/docs/Publishers/agent-site.md b/docs/Publishers/agent-site.md new file mode 100644 index 0000000..e89cd54 --- /dev/null +++ b/docs/Publishers/agent-site.md @@ -0,0 +1,40 @@ +--- +title: Agent Site +deprecated: false +hidden: false +metadata: + robots: index +--- +Your Agent Site, which is automatically set up after you onboard to TollBit, is how you control how the agentic internet sees your content. We want to provide a high level walkthrough of how agents access your content and the different layers of controls you can provide. + +## Whitelisting Bots + +By default, your agent site blocks all bot access. However, there are many circumstances in which you wish to allow certain bots to be able to access your content. The TollBit Agent Site allows you to whitelist specific bots to be able to retrieve your content in Markdown. + +## Monetization + +Monetization is an additional layer of access controls you can provision over your Agent Site. This enforces that all agents that wish you access your content go through the follow workflow. + +### Agent Registration + +When a developer first signs up, they are required to register their user agent to the TollBit Platform. TollBit maintains this global registry of all user agents on the platform, and verifies their identity and connects them to the developer accounts. + +### Requesting Access + +Developers are able to see who is on the TollBit marketplace and which of them are ready to transaction. However, do not initially have any visibility into their rates or licenses. They must request access to publishers through the developer portal, and TollBit will vet each developer before granting them access. + +### Token Generation + +In order to access content, developers must generate TollBit Tokens to include with each of their requests to your agent site. + +Tokens are one-time access grants tied to specific pages and user agents. The token system allows authenticated access for retrieving content, with a one-time use model to ensure security. + +Tollbit tokens are [JWTs](https://datatracker.ietf.org/doc/html/rfc7519) used to authorize a specific content request. They include authentication details, request intent, and, when applicable, pricing and license terms. Tollbit generates and validates tokens automatically; this section explains the token claims for reference. Tokens expire 5 minutes after issuance. + +### Content Intent + +TollBit allows developers to specify their intent when retrieving content, and will be able to serve different types of data with different monetization flows, for each of these intents. These can range from indexing content for building an internal knowledge graph, fetching static content in Markdown for RAG to respond to a user query, or getting a simplified version of the site that preserves key structure to enable faster agentic browsing. + +### Transactions + +Each request is ledgered as a transaction within our system, and all transactions include data around who, what and when it was accessed, the value of the transaction, the license it was retrieved under, and additional metadata that developers pass back, including information about the queries that led to retrieving that content. You are paid out at the end of each month for your total usage across all developers during the previous month. From 0e7b36adcd9fb41fc308d2265268a68bd6b5bb72 Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Fri, 13 Mar 2026 22:44:35 +0000 Subject: [PATCH 10/11] Reorder doc `agent-site` --- docs/Publishers/_order.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Publishers/_order.yaml b/docs/Publishers/_order.yaml index ee47f9d..5cad536 100644 --- a/docs/Publishers/_order.yaml +++ b/docs/Publishers/_order.yaml @@ -1,8 +1,8 @@ - a-tollbooth-for-your-content - properties - integrations +- agent-site - marketplace - other-access-methods - admin - faqs -- agent-site From 66068e389ec09da60198156da3f13ca756b7c965 Mon Sep 17 00:00:00 2001 From: Martin Zhu Date: Fri, 13 Mar 2026 22:46:04 +0000 Subject: [PATCH 11/11] Update doc `agent-site` --- docs/Publishers/agent-site.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Publishers/agent-site.md b/docs/Publishers/agent-site.md index e89cd54..ebd8db7 100644 --- a/docs/Publishers/agent-site.md +++ b/docs/Publishers/agent-site.md @@ -7,11 +7,11 @@ metadata: --- Your Agent Site, which is automatically set up after you onboard to TollBit, is how you control how the agentic internet sees your content. We want to provide a high level walkthrough of how agents access your content and the different layers of controls you can provide. -## Whitelisting Bots +# Whitelisting Bots By default, your agent site blocks all bot access. However, there are many circumstances in which you wish to allow certain bots to be able to access your content. The TollBit Agent Site allows you to whitelist specific bots to be able to retrieve your content in Markdown. -## Monetization +# Monetization Monetization is an additional layer of access controls you can provision over your Agent Site. This enforces that all agents that wish you access your content go through the follow workflow.