x402 Trust

active

trust & reliability data for the x402 ecosystem

Trust and reliability scores for x402 endpoints from continuous 24/7 monitoring: uptime probes, 402-envelope compliance, advertised price history, and real on-chain USDC settlement volume per payTo address. Deterministic and auditable: know before you pay.

DataBasex402 v2exactx402-trust.com ↗︎
Transactions · 30d
0
Volume · 30d
$0.00
Unique buyers · 30d
0
Uptime · 30d
90.2%
Latency p50
332ms
Reported calls · 30d
28

Endpoints (20 live)

  • POST /v1/x402-trust — Trust score (0-100, A-F) for any listed x402 endpoint: uptime, envelope compliance, latency, age, on-chain settlement activity, price stability. Deterministic, auditable breakdown. Re-probes live if the cache is stale. (0.005 USDC on Base)
  • POST /v1/similar — 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. (0.005 USDC on Base)
  • POST /v1/x402-history — 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. (0.02 USDC on Base)
  • POST /v1/x402-trust-bulk-10 — 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` and you are NOT charged. Duplicates are ignored. (0.045 USDC on Base)
  • POST /v1/watch-endpoint-30d — 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. (0.2 USDC on Base)
  • POST /v1/x402-trust-bulk-100 — 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` and you are NOT charged. Duplicates are ignored. (0.325 USDC on Base)
  • POST /v1/x402-trust-bulk-200 — 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` and you are NOT charged. Duplicates are ignored. (0.4 USDC on Base)
  • POST /v1/x402-trust-bulk-50 — 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` and you are NOT charged. Duplicates are ignored. (0.2 USDC on Base)
  • POST /v1/x402-trust-bulk-500 — 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` and you are NOT charged. Duplicates are ignored. (0.5 USDC on Base)
  • POST /v1/semantic-search — Semantic search across the entire monitored x402 catalog. Given a free-text query (e.g. "weather forecast", "image generation", "EVM gas price oracle"), returns the closest endpoints by advertised purpose. Ranking is deterministic: cosine similarity bucketed to whole percentage points first (80.3% and 80.5% are the same bucket), then trust score, then described-before-undescribed, then endpoint id. Matches below a 0.5 cosine-similarity floor are dropped entirely, so a query can return fewer than the requested limit (or none). Endpoints that advertise no description are still matched: they are embedded from their service name and URL path tokens instead of a written description (host name as a last resort). The exact effect of a missing description: no fixed point deduction and no direct similarity malus; the only deterministic penalty is the described-before-undescribed tiebreak (at equal similarity bucket AND equal trust score, a described endpoint ranks first). Beyond that it is purely indirect: the shorter fallback text typically yields lower cosine similarity than a prose description, so such endpoints tend to land in lower similarity buckets, by a query-dependent amount. Each match carries its resource URL, trust score, grade, cosine similarity (0-1, raw value; ranking buckets it), advertised description when present, and a free endpoint-page URL. Matches also carry the advertised price as machine-readable fields: amountUsd (null when not advertised) and priceCeiling (true when the endpoint uses the x402 'upto' scheme, i.e. amountUsd is an authorization ceiling and the real charge is typically lower). This is a DISCOVERY product: it deliberately carries no verdict, recommendation or flag detail (the per-endpoint trust report sold at /v1/x402-trust carries those). The query is embedded with the same model as the catalog, so phrasing the capability you need works better than guessing keywords. (0.001 USDC on Base)
  • GET /v1/x402-trust-bulk-200 (0.4 USDC on Base)
  • GET /v1/semantic-search (0.001 USDC on Base)
  • GET /v1/x402-trust (0.005 USDC on Base)
  • GET /v1/watch-endpoint-30d (0.2 USDC on Base)
  • GET /v1/x402-trust-bulk-10 (0.045 USDC on Base)
  • GET /v1/x402-trust-bulk-50 (0.2 USDC on Base)
  • GET /v1/similar (0.005 USDC on Base)
  • GET /v1/x402-trust-bulk-500 (0.5 USDC on Base)
  • GET /v1/x402-trust-bulk-100 (0.325 USDC on Base)
  • GET /v1/x402-history (0.02 USDC on Base)

First seen · last seen