Content
Content represents the actual payload and data that you are looking for as a developer. You get content by making a request to a specific webpage. Every webpage has its own rate.
Get Content
This endpoint allows you to manually request content of a certain webpage. The <content_path> is simply the full url of the intended webpage.
Required headers
- Name
TollbitToken- Type
- string
- Description
The generated token used to access data one time.
- Name
User-Agent- Type
- string
- Description
Unique User Agent string for who is allowed to access the page. Make sure to use the AgentID that you will use within your application.
Required attributes
- Name
content_url- Type
- string
- Description
The URL that you want to fetch content from.
Response
- Name
content- Type
- object
- Description
Object containing the different sections of the page.
- Name
header- Type
- string
- Description
The header of the page. This contains information such as navigation links and other auxillary information not strictly related to the main purpose of the page.
- Name
main- Type
- object
- Description
The main content of the page, excluding any headers, navigational components, or footers, rendered in markdown for easy parsing.
- Name
footer- Type
- string
- Description
The footer of the page. This contains information such as follow up articles, terms of service, and social media links.
- Name
metadata- Type
- string
- Description
Additional metadata information about the article. The standard metadata fields are
author,description,imageUrl,modified,publishedandtitle.
- Name
rate- Type
- object
- Description
The rate data of this page. See the rate page for additional information.
Request
curl --location 'https://gateway.tollbit.com/dev/v2/content/<content_url>' \
--header 'TollbitToken: eyJhbGciOiJF...' \
--header 'User-Agent: <user_agent>'
Response
{
"content": {
"header": "...",
"main": "December 10, 2023
Up until now, the internet has successfully differentiated humans and bots (at least enough to rely on). But in the age of AI this will not work. Captchas are easily bypassed, and eventually
any user interaction on the internet will probably be navigable by an AI agent. Given this future, why continue to distinguish the two? What were to happen if you opened up the
flood gates to bot mania? Imo, it might actually work to build a newer, more efficient layer of the internet where you dont have to actually navigate page to page. Instead all
a human needs to do is ask for exactly what they want.
When you think about what you do daily on the internet today you probalu think about scrolling on TikTok, X, or checking your email.
Obviously, there are many concerns with such a drastic change to the internet.",
"footer": "..."
},
"metadata": {
"author": "Josh Mayer",
"description": "A short blog article about humans and bots",
"imageUrl": "<image_url>",
"modified": "2023-12-10T13:18:50Z",
"published": "2023-12-10T13:18:50Z",
"title": "New Age of Bots"
},
"rate": {
"license": {
"id": "ji73lwbqjnhfgpu1bk3sjzj1",
"licensePath": "<license_url>",
"licenseType": "ON_DEMAND_LICENSE",
"permissions": [
{
"name": "PARTIAL_USE"
}
]
},
"price": {
"currency": "USD",
"priceMicros": 5000
}
}
}
Self Report Usage
This endpoint allows you to self report your usage asynchonously.
Required headers
- Name
TollbitToken- Type
- string
- Description
The generated token used to access data one time.
- Name
User-Agent- Type
- string
- Description
Unique User Agent string for who is allowed to access the page. Make sure to use the AgentID that you will use within your application.
Required attributes
- Name
idempotencyId- Type
- string
- Description
A unique ID that you generate to ensure idempotency when reporting usage. Useful if you have event driven architecture and may need to deduplicate messages or handle retries.
- Name
usage- Type
- []object
- Description
A list of your usage of different URLs.
- Name
url- Type
- string
- Description
The URL that you wish to report usage on.
- Name
timesUsed- Type
- int
- Description
The number of times you used this particular URL.
- Name
licenseType- Type
- string
- Description
The license type that you used. Currently supports
ON_DEMAND_LICENSE,ON_DEMAND_FULL_USE_LICENSE, andCUSTOM_LICENSE. If you use aCUSTOM_LICENSE, you will need to include alicenseCuidfield with the license ID.
Response
- Name
url- Type
- string
- Description
The URL that you reported usage on.
- Name
perUnitPriceMicros- Type
- int
- Description
The price in micro units of a single use of the URL you reported usage on.
- Name
totalUsePriceMicros- Type
- int
- Description
The total amount of this transaction based on the price per unit and the total usage you reported.
- Name
license- Type
- object
- Description
The license object representing the license you reported usage with.
Request
curl --location 'https://gateway.tollbit.com/tollbit/dev/v2/transactions/selfReport' \
--header 'UserAgent: <user_agent>' \
--header 'TollbitKey: YOUR_API_KEY_HERE' \
--header 'Content-Type: application/json' \
--data '{
"idempotencyId": "1234",
"usage": [
{
"url": "<content_url>",
"timesUsed": 2,
"licenseType": "ON_DEMAND_LICENSE"
},
...
]
}'
Response
[
{
"url": "<content_url>",
"perUnitPriceMicros": 5000,
"totalUsePriceMicros": 10000,
"currency": "USD",
"license": {
"cuid": "ji73lwbqjnhfgpu1bk3sjzj1",
"licenseType": "ON_DEMAND_LICENSE",
"licensePath": "<license_url>",
"permissions": [
{
"name": "PARTIAL_USE"
}
]
}
},
...
]
List Content Catalog
This endpoint allows you to paginate through a flattened sitemap of a particular website.
Required headers
- Name
TollbitToken- Type
- string
- Description
The generated token used to access data one time.
Required attributes
- Name
base_url- Type
- string
- Description
The URL root domain that you want to list the content catalog from.
Response
- Name
pageToken- Type
- string
- Description
The pagination token to fetch the next page.
- Name
pages- Type
- []object
- Description
The pages fetched in the flatten sitemap, ordered by the last modified date (if it exists) descending.
Request
curl --location 'https://gateway.tollbit.com/dev/v2/content/<base_url>/catalog/list' \
--header 'TollbitKey: YOUR_API_KEY_HERE'
Response
{
"pageToken": "example_token",
"pages": [
{
"lastMod": "2025-12-06T02:17:08Z",
"pageUrl": "<page_url_1>",
"propertyId": "example_id"
},
{
"lastMod": "2025-12-06T02:11:49Z",
"pageUrl": "<page_url_2>",
"propertyId": "example_id"
},
...
]
}