Tollbit
TollBit is the web stack for the agentic internet, giving publishers and commerce sites the infrastructure to analyze, control, and monetize AI agent access to their content. Publishers verify a property, stream logs for AI-bot analytics, and stand up an "Agent Site" front door (the tollbit.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Tollbit the way a machine reads it — 15 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Tollbit scores 48.4/100 (developing), with a separate agent-readiness read of 58/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Tollbit
Each block below is one kind of artifact we hold for Tollbit. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Tollbit Auth Tokens API
The Auth Tokens API from Tollbit — 3 operation(s) for auth tokens.
Tollbit Dev API
The Dev API from Tollbit — 1 operation(s) for dev.
Tollbit Get Catalog of Pages for Property API
The Get Catalog of Pages for Property API from Tollbit — 1 operation(s) for get catalog of pages for property.
Tollbit Get Tollbit Content API
The Get Tollbit Content API from Tollbit — 1 operation(s) for get tollbit content.
Tollbit Get Tollbit Rates API
The Get Tollbit Rates API from Tollbit — 2 operation(s) for get tollbit rates.
Tollbit Report Content Usage API
The Report Content Usage API from Tollbit — 1 operation(s) for report content usage.
Tollbit Reporting API
The Reporting API from Tollbit — 1 operation(s) for reporting.
Tollbit Search API
The Search API from Tollbit — 1 operation(s) for search.
Tollbit Search Content API
The Search Content API from Tollbit — 1 operation(s) for search content.
Tollbit Tollbit Content API
The Tollbit Content API from Tollbit — 4 operation(s) for tollbit content.
Tollbit Tollbit Subdomain API
The Tollbit Subdomain API from Tollbit — 1 operation(s) for tollbit subdomain.
Scroll within the panel for all 11 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
tollbit-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
TollBit Content Events (Webhooks)
TollBit pushes real-time webhook notifications to subscriber applications when content becomes available (created or updated) from TollBit publisher properties, so consumers do ...
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Tollbit — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/tollbit · machine-readable index on apis.io