x402 Trust Score

Trust score (0-100, grade A-F) for any x402 endpoint, cataloged or not: 30d uptime, 402-envelope compliance, latency, age, real on-chain USDC settlement volume, and price stability, with a full auditable breakdown. Uncataloged endpoints are live-probed on first query and auto-adopted. Know before you pay.

Raw observation history for one endpoint over 1-90 days: listing and delisting events, price and payTo changes, and probe results with status and latency. Excluded probes (rate limits, unresolved URL templates, our own resolver outages) never count as downtime. probeSummary aggregates the window.

Semantically similar endpoints that currently out-score a given one on the trust score. Each carries score, grade, similarity, advertised price, and endpoint page; same-host siblings and avoid-flagged endpoints are excluded. An empty list means nothing beats the subject.

Monitor one endpoint for 30 days: alerts on payTo, price, asset or network changes, 402-spec regressions, delisting, and liveness. Push to signed HTTPS webhooks or Slack/Discord URLs (max 5 each), all connection-tested before payment. Returns a one-time bearer secret; edit URLs or cancel early via bearer-authed PATCH/DELETE /v1/watch/{id}, or poll the append-only event log.

Score up to 10 x402 endpoints in a single paid call. Each found result carries the FULL trust report — identical to POST /v1/x402-trust: score, grade, scoreRange, recommendation, confidence breakdown, the component/subscore breakdown, explanations, flags + flagsDetailed, advertised price, and 30-day on-chain stats — not just the scalar verdict. Cache rows older than 15 minutes are recomputed on-demand from the latest stored probes and settlements, so scores typically reflect reality within minutes. No live network re-probe is performed — for a fresh live probe use /v1/x402-trust. Per-request recompute limits apply (time + count); results include `recomputed` and `computed_at` so you can see which rows used cached vs freshly computed scores. Resources not in our observation set return `found:false`; you still pay for the batch AS LONG AS at least one resource is tracked. If NONE of the supplied resources are in our observation set the request is rejected with HTTP 400 `notCharged:true`

Score up to 100 x402 endpoints in a single paid call. Each found result carries the FULL trust report — identical to POST /v1/x402-trust: score, grade, scoreRange, recommendation, confidence breakdown, the component/subscore breakdown, explanations, flags + flagsDetailed, advertised price, and 30-day on-chain stats — not just the scalar verdict. Cache rows older than 15 minutes are recomputed on-demand from the latest stored probes and settlements, so scores typically reflect reality within minutes. No live network re-probe is performed — for a fresh live probe use /v1/x402-trust. Per-request recompute limits apply (time + count); results include `recomputed` and `computed_at` so you can see which rows used cached vs freshly computed scores. Resources not in our observation set return `found:false`; you still pay for the batch AS LONG AS at least one resource is tracked. If NONE of the supplied resources are in our observation set the request is rejected with HTTP 400 `notCharged:true`

Score up to 200 x402 endpoints in a single paid call. Each found result carries the FULL trust report — identical to POST /v1/x402-trust: score, grade, scoreRange, recommendation, confidence breakdown, the component/subscore breakdown, explanations, flags + flagsDetailed, advertised price, and 30-day on-chain stats — not just the scalar verdict. Cache rows older than 15 minutes are recomputed on-demand from the latest stored probes and settlements, so scores typically reflect reality within minutes. No live network re-probe is performed — for a fresh live probe use /v1/x402-trust. Per-request recompute limits apply (time + count); results include `recomputed` and `computed_at` so you can see which rows used cached vs freshly computed scores. Resources not in our observation set return `found:false`; you still pay for the batch AS LONG AS at least one resource is tracked. If NONE of the supplied resources are in our observation set the request is rejected with HTTP 400 `notCharged:true`

Score up to 50 x402 endpoints in a single paid call. Each found result carries the FULL trust report — identical to POST /v1/x402-trust: score, grade, scoreRange, recommendation, confidence breakdown, the component/subscore breakdown, explanations, flags + flagsDetailed, advertised price, and 30-day on-chain stats — not just the scalar verdict. Cache rows older than 15 minutes are recomputed on-demand from the latest stored probes and settlements, so scores typically reflect reality within minutes. No live network re-probe is performed — for a fresh live probe use /v1/x402-trust. Per-request recompute limits apply (time + count); results include `recomputed` and `computed_at` so you can see which rows used cached vs freshly computed scores. Resources not in our observation set return `found:false`; you still pay for the batch AS LONG AS at least one resource is tracked. If NONE of the supplied resources are in our observation set the request is rejected with HTTP 400 `notCharged:true`

Score up to 500 x402 endpoints in a single paid call. Each found result carries the FULL trust report — identical to POST /v1/x402-trust: score, grade, scoreRange, recommendation, confidence breakdown, the component/subscore breakdown, explanations, flags + flagsDetailed, advertised price, and 30-day on-chain stats — not just the scalar verdict. Cache rows older than 15 minutes are recomputed on-demand from the latest stored probes and settlements, so scores typically reflect reality within minutes. No live network re-probe is performed — for a fresh live probe use /v1/x402-trust. Per-request recompute limits apply (time + count); results include `recomputed` and `computed_at` so you can see which rows used cached vs freshly computed scores. Resources not in our observation set return `found:false`; you still pay for the batch AS LONG AS at least one resource is tracked. If NONE of the supplied resources are in our observation set the request is rejected with HTTP 400 `notCharged:true`