Methodology
TrustBench is a public registry of x402-style endpoints with nightly liveness telemetry and Ed25519-signed scorecards. This page documents exactly how data is collected, how scores are computed, and what each metric represents — so anyone integrating against the registry knows what they're working with.
Data collection
- ▸A scheduled job runs once per day on a single cloud host.
- ▸For each provider URL, the prober sends three sequential requests per run, sampled across us-east / eu-west / asia-southeast tags. Single host today; multi-host is on the roadmap.
- ▸Each request is HEAD with an 8-second timeout, falling back to GET if the server returns 405.
- ▸HTTP status codes 200, 201, 204, 401, 402, 403, 404, 405, 429 are recorded as "endpoint is alive". Other statuses, connection errors, and timeouts are recorded as failures.
Scoring
score = 15
+ 45 · successRate
+ 35 · latencyHealth // max(0, min(1, 1 - p50 / 2000))
+ 3 · consistencyBonus // max(0, min(1, 1 - jitter))
clamped to [40, 98]
p50 and p95 latency are computed over successful probes only, using linear-interpolation percentiles. Timeouts contribute to reliability but are excluded from the latency calculation, so a single failure does not distort the latency number.
What this measurement does NOT tell you
- •Score reflects reachability and response time, not capability quality. A 4xx or 429 response confirms the endpoint is up and responding, but does not confirm the underlying API behaves correctly when authenticated and paid.
- •Latency is single-origin. All measurements come from one host today. Real-world latency from an agent's location will differ.
- •Payment behavior is not yet measured. The current probe does NOT execute x402 payments, observe settlement latency, or validate payment-gated responses. A capability-aware paid-probe layer ships alongside the router.
- •Scorecards are signed with Ed25519. The public key is served at /.well-known/trustbench-pubkey for any third party to verify a TrustBench scorecard independently.
Verifying a scorecard or receipt
Every scorecard returned by /rankings/paid and every receipt at /receipts/:id carries an Ed25519 signature you can verify offline using the published public key.
Roadmap
Phase 3 router shipped 2026-05-04
First paid x402 receipt: rcpt_01KQY7C44GAPSXZPFQYRZ1D10C — verifiable on-chain.