Tollbit Content API
The Tollbit Content API from Tollbit — 4 operation(s) for tollbit content.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/tollbit:tollbit-tollbit-content-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Tollbit Content API
version: v2
description: 'TollBit is the web stack for the agentic internet: publishers analyze, control, and monetize AI agent access to their content. This API lets developers and AI agents discover licensable content (Licensed Search), fetch rates and license options, mint one-time signed access tokens, retrieve licensed or indexed content, self-report usage, and list a property''s content catalog. Reconstructed by API Evangelist from TollBit''s published per-operation OpenAPI fragments (docs.tollbit.com/reference).'
contact:
name: TollBit
email: team@tollbit.com
url: https://tollbit.com
x-apievangelist:
generated: '2026-07-21'
method: searched
source: https://docs.tollbit.com/reference (per-operation OpenAPI fragments merged; llms.txt index)
note: Reconstructed from TollBit's published per-operation OpenAPI 3.0 fragments. Only real /dev/* and subdomain endpoints included; a foreign ReadMe sample spec present on two reference pages was excluded.
servers:
- url: https://gateway.tollbit.com
description: Production API gateway
tags:
- name: Tollbit Content
paths:
/dev/v2/content/{contentUrl}:
get:
operationId: ContentService_getContent
parameters:
- name: contentUrl
in: path
required: true
schema:
type: string
responses:
'200':
description: The request has succeeded.
content:
application/json:
schema:
$ref: '#/components/schemas/GetContentResponse'
'400':
description: The server could not understand the request due to invalid syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'401':
description: Access is unauthorized.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'403':
description: Access is forbidden.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'404':
description: The server cannot find the requested resource.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'500':
description: Server error
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
tags:
- Tollbit Content
security:
- ApiKeyAuth_: []
summary: Content service get content
x-summary-source: derived
/dev/v2/content/{propertyDomain}/catalog/list:
get:
operationId: ContentService_getCatalog
parameters:
- name: propertyDomain
in: path
required: true
schema:
type: string
- name: pageSize
in: query
required: false
schema:
type: integer
format: int32
explode: false
- name: pageToken
in: query
required: false
schema:
type: string
explode: false
responses:
'200':
description: The request has succeeded.
content:
application/json:
schema:
$ref: '#/components/schemas/CatalogResponse'
'400':
description: The server could not understand the request due to invalid syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'401':
description: Access is unauthorized.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'403':
description: Access is forbidden.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'404':
description: The server cannot find the requested resource.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'500':
description: Server error
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
tags:
- Tollbit Content
security:
- ApiKeyAuth: []
summary: Content service get catalog
x-summary-source: derived
/dev/v2/rates/batch:
post:
operationId: ContentService_batchGetRates
parameters: []
responses:
'200':
description: The request has succeeded.
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/BatchRateResponseV2'
'400':
description: The server could not understand the request due to invalid syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'401':
description: Access is unauthorized.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'403':
description: Access is forbidden.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'404':
description: The server cannot find the requested resource.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'500':
description: Server error
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
tags:
- Tollbit Content
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/BatchGetRateRequest'
security:
- ApiKeyAuth: []
summary: Content service batch get rates
x-summary-source: derived
/dev/v2/rates/{contentUrl}:
get:
operationId: ContentService_getRates
parameters:
- name: contentUrl
in: path
required: true
schema:
type: string
responses:
'200':
description: The request has succeeded.
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/DeveloperRateResponse'
'400':
description: The server could not understand the request due to invalid syntax.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'401':
description: Access is unauthorized.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'403':
description: Access is forbidden.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'404':
description: The server cannot find the requested resource.
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
'500':
description: Server error
content:
application/json:
schema:
$ref: '#/components/schemas/ProblemJSON'
tags:
- Tollbit Content
security:
- ApiKeyAuth: []
summary: Content service get rates
x-summary-source: derived
components:
schemas:
BatchRateLicenseResponse:
type: object
required:
- cuid
- licenseType
- licensePath
- permissions
- validUntil
properties:
cuid:
type: string
licenseType:
type: string
licensePath:
type: string
permissions:
type: array
items:
$ref: '#/components/schemas/RateLicensePermission'
validUntil:
type: string
ContentRate:
type: object
required:
- price
- license
properties:
price:
$ref: '#/components/schemas/RatePrice'
license:
$ref: '#/components/schemas/RateLicenseResponse'
BatchDeveloperRateResponse:
type: object
required:
- price
- license
- error
properties:
price:
$ref: '#/components/schemas/RatePriceResponse'
license:
$ref: '#/components/schemas/BatchRateLicenseResponse'
error:
type: string
DeveloperRateResponse:
type: object
required:
- price
- license
properties:
price:
$ref: '#/components/schemas/RatePrice'
license:
$ref: '#/components/schemas/RateLicenseResponse'
PropertyPage:
type: object
required:
- propertyId
- pageUrl
properties:
propertyId:
type: string
pageUrl:
type: string
lastMod:
type: string
format: date-time
ContentMetadata:
type: object
properties:
title:
type: string
description:
type: string
imageUrl:
type: string
author:
type: string
published:
type: string
modified:
type: string
RatePriceResponse:
type: object
required:
- priceMicros
- currency
properties:
priceMicros:
type: integer
format: int64
currency:
type: string
PageContent:
type: object
required:
- header
- body
- footer
properties:
header:
type: string
body:
type: string
footer:
type: string
GetContentResponse:
type: object
required:
- content
- metadata
properties:
content:
$ref: '#/components/schemas/PageContent'
metadata:
$ref: '#/components/schemas/ContentMetadata'
rate:
$ref: '#/components/schemas/ContentRate'
RateLicensePermission:
type: object
required:
- name
properties:
name:
type: string
BatchRateResponseV2:
type: object
required:
- url
- rates
properties:
url:
type: string
rates:
type: array
items:
$ref: '#/components/schemas/BatchDeveloperRateResponse'
ProblemJSON:
type: object
required:
- type
- title
- status
properties:
type:
type: string
title:
type: string
status:
type: integer
format: int32
detail:
type: string
instance:
type: string
additionalProperties: {}
CatalogResponse:
type: object
required:
- pages
properties:
pageToken:
type: string
pages:
type: array
items:
$ref: '#/components/schemas/PropertyPage'
RatePrice:
type: object
required:
- priceMicros
- currency
properties:
priceMicros:
type: integer
format: int64
currency:
type: string
RateLicenseResponse:
type: object
required:
- id
- licenseType
- licensePath
- permissions
properties:
id:
type: string
licenseType:
type: string
licensePath:
type: string
permissions:
type: array
items:
$ref: '#/components/schemas/RateLicensePermission'
BatchGetRateRequest:
type: object
required:
- urls
properties:
urls:
type: array
items:
type: string
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: TollbitKey
ApiKeyAuth_:
type: apiKey
in: header
name: Tollbit-Token
TollbitKey:
type: apiKey
in: header
name: TollbitKey
description: Your API key which can be found in the access page of the dashboard.
SubdomainAccessToken:
type: http
scheme: Bearer
description: 'To access content on a TollBit subdomain, you will need an access token. This token is a JWT that is signed by TollBit and includes information about the subdomain and the permissions granted to the token.
You can obtain the token by calling the TokensService to create a Content Access Token. Once you have the token, you can include it in the Authorization header of your requests to the subdomain.'