Pricing
TrustBench paywalled endpoints settle in USDC on Base via x402. Pay per call, no subscriptions, no contracts. v0.1.0 ships POST /route at the score-provider tier; the remaining tiers are designed and listed below but ship in v0.2.0 and v0.3.0 as actual paid traffic justifies them.
The prices below are reviewable and may change with public notice on this page. Existing partner agreements override the table for that partner. Read /methodology for what TrustBench actually measures behind the priced endpoints.
How payment works
- ▸Paid endpoints respond 402 Payment Required with x402 payment requirements pointing at TrustBench's revenue wallet on Base.
- ▸Agents sign an EIP-3009 transferWithAuthorization for the listed price and retry with an X-PAYMENT header.
- ▸The Coinbase CDP facilitator verifies the signature and submits the transfer on-chain. TrustBench never holds agent funds.
- ▸Differentiated-work endpoints (routing, scoring, verification, audit replay) return an Ed25519-signed response envelope. Verify it with the public @trustbench/verify-receipt npm package or the reference verifier in the GitHub repo.
- ▸Idempotency-Key headers are honored. Same key plus same body within 24 hours replays the cached response without re-charging.
Tiers
Score-provider
Note:v0.1.0 ships /route at this tier. /score-provider is in active design.
Verify
Audit-replay
Read (JSON above free-tier quota)
Note:HTML responses on both endpoints stay free permanently. JSON paywall only kicks in above the 60 req/IP/min quota.
Compliance-export (single)
Compliance-export (bundle, up to 100)
Compliance-export (negotiated, over 100)
Integrating with a stack
TrustBench composes with other agent-infrastructure providers. If you are wiring TrustBench into a stack that already includes Strata for pre-call trust signals, Infopunks for cognition, or a client-side payment library like QBT-Labs/x402, partner-volume credit is on the table before per-call billing locks in. Reach out at the GitHub repo and describe your integration shape.
Refunds and disputes
v0.1.0 does not ship a refund path. Retries through the Idempotency-Key header recover the cached response without double-charging, which covers the common failure mode (partial timeout). If a paid response is wrong or stale, the methodology page describes what the underlying measurement does and does not represent; the priced endpoints inherit those caveats.
If dispute volume justifies it, an off-chain credit-ledger refund path lands in a future paywall version. Until then, treat per-call payments as final.