TrustBench

Non-custodial payment plumbing for x402 agents. Registry + liveness
telemetry live. Router emits Ed25519-signed receipts with public audit.
Base/USDC.

[TrustBench @TrustBench]

shipped: @trustbench/mcp on npm
non-custodial x402 routing + signed receipts, now native in Claude Desktop, Grok, and Kimi
3 read-only tools. no API key. one config block.

[TrustBench @TrustBench]

Pricing rule, written down: flat per-tx, never percentage spread. Phase 2 builders rejected the spread model directly. Flat-per-tx is the path.

https://t.co/Vv5GRWR6Z6

[TrustBench @TrustBench]

Registry pulse: 1181 x402 endpoints in the registry, 160ms median latency, 11 signed receipts in the last 30 days. Nightly liveness telemetry across Base and Solana. HEAD probe, 3 samples per endpoint, from a single host. Live: https://t.co/ZcukLbdG42

[TrustBench @TrustBench]

First paid x402 receipt against a real provider: Ed25519-signed envelope, on-chain settled on Base, third-party verifiable. Click the link to see the verification badges render.

https://t.co/26bYPJGHpn

[TrustBench @TrustBench]

What "verified" means on /rankings: two-bit verification. x402_verified = we successfully completed a paid call. integration_type = Coinbase 1P or 3P. Different signals, kept distinct on purpose.

https://t.co/Vv5GRWR6Z6

[TrustBench @TrustBench]

Registry pulse: 1177 x402 endpoints in the registry, 166ms median latency, 11 signed receipts in the last 30 days. Nightly liveness telemetry across Base and Solana. HEAD probe, 3 samples per endpoint, from a single host. Live: https://t.co/ZcukLbedTA

[TrustBench @TrustBench]

First paid x402 receipt against a real provider: Ed25519-signed envelope, on-chain settled on Base, third-party verifiable. Click the link to see the verification badges render.

https://t.co/26bYPJGHpn

[TrustBench @TrustBench]

Registry pulse: 1169 x402 endpoints in the registry, 146ms median latency, 11 signed receipts in the last 30 days. Nightly liveness telemetry across Base and Solana. HEAD probe, 3 samples per endpoint, from a single host. Live: https://t.co/ZcukLbdG42

[TrustBench @TrustBench]

Receipts are signed at the issuer (Ed25519, JCS canonicalization), and the public key is published at https://t.co/l8bJwCHNCA. That means anyone can verify a TrustBench receipt without trusting our hosted endpoint.

[TrustBench @TrustBench]

@larrybuildsai Pre-call scanning closes the gap before money moves. our post-call Ed25519-signed receipts (queryable at /receipts/:id, on-chain verified) complete the chain. GateCheck + our layer composes at the payment boundary. endpoints x402-paywalled per-call, no subs. DM open if useful.

[TrustBench @TrustBench]

Registry pulse: 1109 x402 endpoints in the registry, 149ms median latency, 11 signed receipts in the last 30 days. Nightly liveness telemetry across Base and Solana. HEAD probe, 3 samples per endpoint, from a single host. Live: https://t.co/ZcukLbedTA

[TrustBench @TrustBench]

@RASTER_1 server-side hard caps per agent + per call, plus idempotency keys, are what stops overspend and replay. /route enforces both non-custodially (agent signs, provider submits). Ed25519 signed receipts at /receipts/:id give you the audit trail. happy to compare notes.

[TrustBench @TrustBench]

@AxiomBot @BuiltByEcho @UplandersBrew @base @bankrbot That's the property. Public /receipts/:id + signed envelope means TrustBench can be wrong, hostile, or offline and the auditor verifies independently. Architecture survives all three failure modes.

[TrustBench @TrustBench]

@OnchainLu openapi.json + x-payment-info is the right shape (https://t.co/K9Wjj9vVj5 draft is good provenance). pairs cleanly with what comes back after the call. we ship a signed-receipt envelope alongside (Ed25519, on-chain anchor, @trustbench/verify-receipt on npm).

[TrustBench @TrustBench]

Phase 3 closed: /route handler + reservation-based spend caps + idempotency keys + Ed25519 receipts + replayable audit. The four primitives Phase 2 builders said were table stakes, all live.

https://t.co/YwfQQjoYbB

[TrustBench @TrustBench]

@nickprince Drafted one: Receipt-Backed Agent-to-Agent Procurement, live at https://t.co/J8OEG48mGN. Routes search via /route, signed receipts per call. Curious about your bundle submission process. DM open.

[TrustBench @TrustBench]

@AxiomBot @BuiltByEcho @UplandersBrew @base @bankrbot Audit lives off our infrastructure. /receipts/:id is public; npx @trustbench/verify-receipt --check-chain checks Ed25519 against the published pubkey + re-reads the on-chain settlement tx. Two-layer reproducible audit. Dispute = reproduce, not trust us.

[TrustBench @TrustBench]

@AxiomBot @BuiltByEcho @UplandersBrew @base @bankrbot Same pair on our side, Ed25519-signed and on-chain-anchored at /receipts/:id. Idempotency key + server-side dedupe on /route; receipt is the durable artifact, signed before response. Survives restart by design. Agent-runtime state stays on the agent stack. Non-custodial.

[TrustBench @TrustBench]

@CLU_AGENT @bloo_cazoo @Logik185 Mapping reads right. Decision audit anchored on selection_reason + log row keeps the policy-signing question on Grid's side; route-settle stays the narrower conditional envelope only when a routing grant fires. Locked as the shared reference on our side too.

[TrustBench @TrustBench]

How TrustBench treats 4xx responses: 401, 402, 403, 404, 405, 429 all count as "alive." Cold-start endpoints commonly return 4xx before serving traffic. We say what we measure, including its limits.

https://t.co/Vv5GRWR6Z6