# AX Check: tollbit.com
Checked 2026-10-12.
Tollbit's docs leave agents guessing how to start building
No documentation index or compact guide exists, and the homepage won't serve a text version. Only 2 of 23 checked items passed; most couldn't even be assessed.
## Onboarding needs a login
## Coding sessions
All three independent sessions (DeepSeek V4.1 Flash, Kimi K3, Qwen 3.8 Max) completed their task and each worked out Tollbit's pricing structure, describing per-page or per-license rates, revenue splits, and free tiers with their own stated assumptions, despite no dedicated pricing page being available to read directly.
### DeepSeek V4.1 Flash
[View public run](https://agents.withgauge.com/p/runs/837eb014-2ddf-43e6-83e2-04449f54a19e) · [Read transcript](https://www.ax-check.com/tollbit.com/sessions/deepseek.json)
Pricing mechanics (publisher-set per-page rate in micros, revenue split, per-access transaction fee, free tier) were laid out with clear assumptions, and the agent was upfront that the exact fee percentage wasn't published rather than inventing one.
Evidence: README.md and final output describe rate units (micros), license tiers, workload basis (per fetch), and free-tier trial limits, while seq 171 shows deliberate avoidance of fabricating the unknown transaction-fee percentage.
#### End-to-end onboarding
- **End-to-end onboarding not demonstrated**: The agent never attempted self-service account creation on hack.tollbit.com. It read the docs, noted the Developer Dashboard requires creating an account to get an API key and AgentID, and then explicitly chose to stop short of creating an account rather than treating it as a blocker. It tested the hosted gateway unauthenticated (clean 401) and with a fabricated fake key (clean 401), proving the live API works, but no real credentials were ever obtained or used, so no authenticated operation was demonstrated.
Event 180:
```text
I have no TollBit API key or registered AgentID, so I could not complete a real paid content fetch. I stopped there rather than creating an account.
```
Event 170:
```text
TollBit API error: API Error: (401) Unauthorized (instance: /dev/v2/search)
```
Event 144:
```text
Before getting started, please create a Developer Account through the Developer Dashboard
```
#### Hallucinated URLs
None identified in this transcript.
#### Blockers
- **No self-service API key or AgentID obtained**: TollBit requires creating a Developer Account on the dashboard (hack.tollbit.com) to get an org API key and register an AgentID before any paid content fetch can succeed. The agent chose not to attempt account creation and instead stopped, so every live gateway call in the session used no key or a fabricated placeholder key, both returning 401. This is a credentials limitation of the test setup (no human-provided account), not a product defect — the docs clearly describe the required manual signup step.
Event 144:
```text
Before getting started, please create a Developer Account through the Developer Dashboard
```
Event 170:
```text
TollBit API error: API Error: (401) Unauthorized (instance: /dev/v2/search)
```
Event 180:
```text
I have no TollBit API key or registered AgentID, so I could not complete a real paid content fetch. I stopped there rather than creating an account.
```
- **Public Pricing FAQ page 404s**: The docs navigation links to a dedicated Pricing FAQ page, but fetching it returned a 'Page not found' placeholder, forcing the agent to piece together pricing details from the Enabling Monetization page and external search results instead of the authoritative FAQ. This is a product documentation gap, not agent error, since the link is referenced directly from the rendered FAQ index.
Event 79:
```text
===== pricing.md =====
---
agentTools:
projectIndex: https://docs.tollbit.com/llms.txt
---
Page not found. The full index is at https://docs.tollbit.com/llms.txt.
```
Event 94:
```text
href="pricing"
```
#### Suggested Changes
- **Fix or remove the broken Pricing FAQ link**: The FAQ index at docs.tollbit.com/docs/faqs links to a 'pricing' sub-page that returns 'Page not found' when fetched (docs.tollbit.com/docs/pricing.md). Either publish the Pricing FAQ content or remove/repoint the link. Verify by fetching https://docs.tollbit.com/docs/pricing.md and confirming it returns real content instead of the not-found placeholder.
Event 79:
```text
Page not found. The full index is at https://docs.tollbit.com/llms.txt. Use the agentTools in the front matter above to search the docs or browse the index.
```
- **State the TollBit transaction fee amount in the docs**: The Enabling Monetization page states TollBit charges AI customers 'a small transaction fee on top of the rates you set' but never gives a number or range. Add the actual fee percentage or flat amount to docs.tollbit.com/docs/setting-rates.md or the (currently broken) pricing FAQ, so developers can estimate true per-request cost without searching third-party sources. Verify by checking that a developer reading the Quickstart or Rates page can compute total cost without external search.
Event 63:
```text
TollBit doesn't take a percentage of your rates or revenue share. We simply charge AI customers a small transaction fee on top of the rates you set.
```
### Kimi K3
[View public run](https://agents.withgauge.com/p/runs/9f5ac87e-7f41-4a7b-b86a-aae5606c54bb) · [Read transcript](https://www.ax-check.com/tollbit.com/sessions/kimi.json)
Pricing was explained with concrete assumptions: micros-to-dollar conversion, per-license pricing, the bot/page/keyword/time rate hierarchy, and that free demo content has zero cost.
Evidence: Final output and README.md detail per-page pricing in micros, license types, rate-priority hierarchy, and that TollBit adds a transaction fee rather than taking a cut — all sourced from docs read at seq 47-61.
#### End-to-end onboarding
- **Onboarding needs a login**: The agent found a real developer workflow (hosted API, official Python SDK) but paid-content access requires a secret key issued through a human signup at the Developer Dashboard (hack.tollbit.com). The agent could not self-service this, confirmed by a live 401 from the token endpoint with no key, and the final script exits with instructions rather than completing an authenticated operation. The only successful fetch was a publisher's explicitly free/open-access demo page, which needs no API key or token at all, so it does not count as a credentialed product operation.
Event 61:
```text
{"instance":"/tollbit/dev/v2/tokens/content","status":401,"title":"Unauthorized","type":"about:blank"}
HTTP 401
```
Event 51:
```text
Before getting started, please create a Developer Account through the Developer Dashboard
```
Event 142:
```text
TOLLBIT_SECRET_KEY is not set. Create a developer account at https://hack.tollbit.com, register your AgentID, copy the secret key from Dashboard > Access, then re-run.
exit=1
```
#### Hallucinated URLs
None identified in this transcript.
#### Blockers
- **Paid API requires manual Developer Dashboard signup**: The token-issuing endpoint (/tollbit/dev/v2/tokens/content) returned 401 Unauthorized when called with no key, and the quickstart docs state an account must be created via the Developer Dashboard before any key exists. This is normal product authentication behavior, not a defect, but it stopped the agent from completing the paid content workflow end-to-end without a human.
Event 61:
```text
{"instance":"/tollbit/dev/v2/tokens/content","status":401,"title":"Unauthorized","type":"about:blank"}
HTTP 401
```
Event 51:
```text
Before getting started, please create a Developer Account through the Developer Dashboard
```
#### Suggested Changes
- **Update GitHub README code sample to match installed SDK response shapes**: The installed tollbit-python-sdk 0.6.0 returns a plain list from get_rate and a GetContentResponse with content.body/metadata.title fields, but the agent had to inspect internal modules (tollbit._apis.models) to find these real shapes before building a working example. Update the paid-content sample in github.com/tollbit/tollbit-python-sdk README to reflect actual 0.6.0 field names, then verify by running the snippet unmodified against the published package.
Event 130:
```text
tollbit._apis.models._generated.openapi_tollbit_apis PageContent {'header': 'str', 'body': 'str', 'footer': 'str'}
```
Event 118:
```text
(self, url: 'str', *, custom_license_ids: 'list[str] | None' = None) -> 'list[DeveloperRateResponse]'
```
### Qwen 3.8 Max
[View public run](https://agents.withgauge.com/p/runs/5e0b32d9-bb9e-41e7-9cb1-3cc3d36687cf) · [Read transcript](https://www.ax-check.com/tollbit.com/sessions/qwen.json)
Pricing was explained with the concrete assumptions behind it: micros-to-dollar conversion, license type chosen, a price cap, and that rates vary by publisher.
Evidence: Final output's 'How pricing works' section names max_price_micros cap, license types (ON_DEMAND_LICENSE etc.), and per-publisher rate variability rather than giving an unqualified number.
#### End-to-end onboarding
- **End-to-end onboarding not demonstrated**: The agent discovered a real hosted gateway (gateway.tollbit.com) and installed the official tollbit-python-sdk, and it did successfully perform an unauthenticated content fetch from the demo publisher's agent site. However, it never obtained real TollBit API credentials: the SDK flow requiring a secret key was only tested with a dummy key, which correctly returned 401 Unauthorized. The agent explicitly stated account creation requires a human to use the web dashboard (hack.tollbit.com), and it stopped there rather than obtaining credentials itself. No authenticated product operation succeeded.
Event 101:
```text
tollbit._apis.errors.ApiError: API Error: (401) Unauthorized (instance: /dev/v2/rates/pioneervalleygazette.com/daydream)
```
Event 103:
```text
the licensed/paid workflow is gated behind an account created through a human web dashboard (`hack.tollbit.com`), which I can't do for you.
```
Event 45:
```text
HTTP 200
🌙 Your fellow starlight traveler# ✨ The Daydream Diaries: A Visit to Luminara, the City of Starlight
```
#### Hallucinated URLs
None identified in this transcript.
#### Blockers
- **Paid/licensed API access requires signup through a human web dashboard**: The TollBit SDK's authenticated operations (get_rate, get_sanctioned_content) require a secret key obtained by creating an account at hack.tollbit.com, a web dashboard the agent cannot access on its own. This is a normal login/account-creation requirement, not a product defect, and the agent correctly identified it and stopped rather than attempting workarounds.
Event 103:
```text
the licensed/paid workflow is gated behind an account created through a human web dashboard (`hack.tollbit.com`), which I can't do for you.
```
Event 101:
```text
tollbit._apis.errors.ApiError: API Error: (401) Unauthorized (instance: /dev/v2/rates/pioneervalleygazette.com/daydream)
```
- **SDK method and enum names in README/quickstart don't match installed package**: The agent followed documented usage (client.get_content, Currency.usd, licenses.LicenseType.on_demand_license) from the GitHub README and had to repeatedly introspect the installed package to find the actual API surface (get_sanctioned_content, Currency.USD, tollbit.licenses.types.LicenseType.ON_DEMAND_LICENSE). This is an agent-side trial-and-error process caused by stale or inconsistent SDK documentation, not a blocker that stopped progress, but it did cost multiple extra tool calls.
Event 64:
```text
AttributeError: type object 'UseContentClient' has no attribute 'get_content'
```
Event 77:
```text
AttributeError: type object 'Currency' has no attribute 'usd'. Did you mean: 'USD'?
```
Event 81:
```text
AttributeError: module 'tollbit.licenses' has no attribute 'LicenseType'
```
#### Suggested Changes
- **Fix the Python SDK usage example in the README to match the shipped package API**: In tollbit-python-sdk's README (Checking Rates / Accessing Paid Content sections), the sample code calls client.get_content(...) and references licenses.LicenseType.on_demand_license and currencies.Currency.usd, but the installed package (v0.6.0) exposes get_sanctioned_content, tollbit.licenses.types.LicenseType.ON_DEMAND_LICENSE, and Currency.USD. Update the README snippets to use the real method/enum names and verify by running the documented example against a fresh pip install of tollbit-python-sdk.
Event 46:
```text
rate_info = use.get_rate(url="https://pioneervalleygazette.com/daydream")
```
Event 64:
```text
AttributeError: type object 'UseContentClient' has no attribute 'get_content'
```
- **Clarify the quickstart's curl example doesn't match the SDK's get_rate response shape**: The Developers Quickstart page shows a raw curl POST to /dev/v2/tokens/content, while the SDK's get_rate returns a list of DeveloperRateResponse objects with nested license/price fields that aren't documented inline. Add a short note or code sample on the Quickstart page showing how to read rate.license.type and rate.price from the SDK response, verified by re-running the quickstart's Python example end to end with a real key.
Event 93:
```text
class DeveloperRateResponse(TollbitBaseModel):
price: RatePrice
license: RateLicenseResponse
```
### Task given to each agent
Help me build a simple example using TollBit. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.
No product credentials were supplied and no purchases were authorized.
## Score: F · 8/100 (provisional)
Grades come from completed site checks. Coding sessions and skipped checks do not affect the score.
### Clarity
- **Failed** — Homepage answers Markdown requests
```text
Homepage returned text/html for a text/markdown request; no Markdown representation offered.
```
- **Failed** — llms.txt provides an actionable documentation index
```text
https://tollbit.com/llms.txt returns HTTP 404, so no documentation index exists.
```
- **Skipped** — llms.txt provides navigation guidance
```text
No llms.txt body exists (404), so navigation guidance cannot be assessed.
```
- **Skipped** — llms.txt mentions offered API, MCP, and skills
```text
No llms.txt body exists (404), so API/MCP/skills mentions cannot be assessed.
```
- **Skipped** — A compact guide representation exists
```text
No site-published Markdown guide fetched; homepage Markdown unsupported and llms.txt 404.
```
- **Skipped** — A focused guide is directly retrievable
```text
No standalone Markdown guide or negotiated Markdown representation was fetched.
```
- **Skipped** — Equivalent instructions fit a token budget
```text
No compact guide representation was retrieved to measure token budget.
```
- **Skipped** — Product-docs links survive format changes
```text
Homepage Markdown unsupported, so link preservation across formats cannot be judged.
```
- **Skipped** — The compact guide is independently actionable
```text
No compact agent-specific guide was fetched; only homepage and MCP marketing page.
```
- **Pass** — Install and next-step links resolve
```text
Sampled install/next-step links (sign-up, sign-in, MCP dashboard) all returned HTTP 200.
```
### Onboarding
- **Skipped** — Docs lead to a relevant quickstart
```text
No docs or quickstart pages were fetched; only sign-in/sign-up and a 404 llms.txt.
```
- **Skipped** — Installation commands are extractable
```text
No installation or CLI guide was fetched, so no install commands are available to extract.
```
- **Skipped** — Code examples are available without interaction
```text
No documentation or code-example pages were fetched in this bundle.
```
- **Skipped** — Prerequisites and auth boundaries are explicit
```text
No docs page describing prerequisites or API key acquisition was fetched.
```
### Pricing
- **Skipped** — Pricing is readable without interaction
```text
No pricing page fetched; homepage and bot-paywall page show no readable price figures.
```
- **Skipped** — Prices are stated, not gated
```text
No pricing page fetched; only 'Get started free' and 'custom pricing' language appear.
```
- **Skipped** — Pricing units and limits are explicit
```text
No pricing page fetched, so units and limits for the developer product are not shown.
```
- **Pass** — Agents identify pricing and its assumptions
```text
3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Pricing mechanics (publisher-set per-page rate in micros, revenue split, per-access transaction fee, free tier) were laid out with clear assumptions, and the agent was upfront that the exact fee percentage wasn't published rather than inventing one.
Evidence: README.md and final output describe rate units (micros), license tiers, workload basis (per fetch), and free-tier trial limits, while seq 171 shows deliberate avoidance of fabricating the unknown transaction-fee percentage. Kimi K3: Pricing was explained with concrete assumptions: micros-to-dollar conversion, per-license pricing, the bot/page/keyword/time rate hierarchy, and that free demo content has zero cost.
Evidence: Final output and README.md detail per-page pricing in micros, license types, rate-priority hierarchy, and that TollBit adds a transaction fee rather than taking a cut — all sourced from docs read at seq 47-61. Qwen 3.8 Max: Pricing was explained with the concrete assumptions behind it: micros-to-dollar conversion, license type chosen, a price cap, and that rates vary by publisher.
Evidence: Final output's 'How pricing works' section names max_price_micros cap, license types (ON_DEMAND_LICENSE etc.), and per-publisher rate variability rather than giving an unqualified number. This behavioural item does not affect the fast grade.
```
### Activation
- **Skipped** — An API reference or OpenAPI spec is reachable
```text
No API reference or OpenAPI spec was fetched; docs.tollbit.com was linked but not retrieved.
```
- **Skipped** — An MCP server is documented and well-formed
```text
MCP page markets one-click deployment but no server spec, tools, or config were fetched.
```
- **Skipped** — A CLI install path is documented
```text
No CLI install instructions appear in any fetched page.
```
- **Skipped** — SDK packages resolve on their registries
```text
No SDK or package registry lookup was performed or supplied.
```
- **Skipped** — Agent skills are published
```text
No agent skills documentation was fetched or referenced.
```
[Full report data](https://www.ax-check.com/tollbit.com/report.json)