Claim verification for your product.

Submit one claim and inspect the recorded outcome, available evidence and limitations. Some responses say confidence is unavailable. A check may produce or reuse a public receipt. Do not submit confidential or personal information.

Example request

POST /v1/verify
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{ "claim": "A claim to check" }

Pricing

Included with your plan.

Bro includes 100 API calls a month. Pro includes 1,000. A call is one request that returns a judgment; failed checks do not count. Included calls reset on the 1st (UTC). Past them, or with no plan, each call draws on a prepaid wallet at the prices below. Successful responses carry X-TMB-Calls-Remaining.

Wallet prices, per request.

The engine determines whether a recorded receipt can be reused. A familiar claim does not guarantee reuse. A completed check may still be charged when evidence is insufficient and no public receipt is produced; inspect the returned status and cost.

What you asked for	Per claim	Per 1,000
Retrieved from the corpusAn existing receipt is accepted for reuse by the engine.	$0.003	$3.00
Constructed by the engineThe engine performs a check without verified receipt reuse. Evidence and publication are not guaranteed.	$0.01	$10.00

Check the returned cost
and balance

Reuse can reduce the request price

A request with verified receipt reuse has the lower price above. The reuse rate depends on the claims and available records; future reuse or savings are not guaranteed.

Getting a key

Sign up, pick a plan or load a wallet*.

Create an account. Email and password, same account as the app. We need a real identity behind a key so a leaked one can be revoked and so abuse has a name attached to it.
Generate a key. One click in your dashboard. We show it once and store a hash, so if you lose it we cannot recover it and neither can anyone who reads our database. Send it as Authorization: Bearer tmb_live_…
Use your included calls. On Bro or Pro, calls come out of the monthly allowance first and cost nothing extra.
Spend your free credit. Every new account also gets $0.10 of wallet credit, no card. *That is 33 claims already in the corpus, or 10 the engine has to construct from scratch, or a mix at the prices above.
Top up when you need more. Load between $5.00 and $50.00 at a time. No seat fees, no minimum monthly spend. The balance does not expire.
Inspect each response. Successful responses include X-TMB-Billing (included or wallet), X-TMB-Calls-Remaining, X-TMB-Cost, X-TMB-Balance and X-TMB-Source. Handle status codes separately: not every error includes these headers. When included calls and the wallet are both empty you get 402 with top-up and upgrade links.

Rate limits

Per account, across all your keys: Pro 60 a minute and 1,000 an hour; Bro and wallet-only accounts 10 a minute and 300 an hour. Completed calls are counted across every server instance. A 429 response includes Retry-After. Avoid blind retries after an uncertain response: a lost reply does not prove the work was cancelled or uncharged.

The honest part

What the API does not include.

The API is the engine's judgement, one claim at a time. Know what it leaves out before you wire it up.

JSON results, with possible public receipts. Result fields include balance_verdict, for_sources, against_sources, summary, note and receipt_id. A published or reused result can have a public receipt ID; other outcomes may have no ID. Read unavailable confidence markers in confidence_breakdown instead of interpreting a compatibility zero as a measured score. The source field describes retrieved or constructed billing classification, not a bibliographic source.

One claim per call. Up to 600 characters. Send each claim as its own request.

Bibliographic fields vary. Source records contain the metadata available for that source. Authors, dates, DOI, venue and other fields may be missing. Validate identity and support before formatting citations; do not invent missing details.

No interface. No extension, no side panel, no library, no export. If you want a person to use this rather than a program, they want the app.

It is the same engine without the surfaces that make it usable by a human. If you are checking claims inside your own product, that is the right trade. If you are the one reading the answer, the extension is. Both come with every plan.

Get a key

Already have an account? Open your wallet and generate a key. Not yet? Leave an email and we will send you the steps.

Or join the general early-access waitlist and get the API, the extension and the full wiki as each one opens.