Find better alternatives to an x402 endpoint. Given a resource URL, returns the top semantically-similar endpoints (matched on advertised purpose via description embeddings) that currently OUT-SCORE it on our deterministic trust score — so an agent about to pay a mediocre endpoint can discover a more reliable, better-settled one serving the same function. Each result carries its trust score, grade, cosine similarity, advertised price and free endpoint-page URL. The price fields stay machine-readable: amountUsd is always the raw advertised amount, and the separate boolean priceCeiling is true when the endpoint uses the x402 'upto' scheme, i.e. amountUsd is an authorization ceiling and the real charge is typically lower. Same-host siblings and 'avoid'-flagged endpoints are excluded. Returns an empty list (still a valid answer) when nothing beats the subject.
Find better alternatives to an x402 endpoint. Given a resource URL, returns the top semantically-similar endpoints (matched on advertised purpose via description embeddings) that currently OUT-SCORE it on our deterministic trust score — so an agent about to pay a mediocre endpoint can discover a more reliable, better-settled one serving the same function. Each result carries its trust score, grade, cosine similarity, advertised price and free endpoint-page URL. The price fields stay machine-readable: amountUsd is always the raw advertised amount, and the separate boolean priceCeiling is true when the endpoint uses the x402 'upto' scheme, i.e. amountUsd is an authorization ceiling and the real charge is typically lower. Same-host siblings and 'avoid'-flagged endpoints are excluded. Returns an empty list (still a valid answer) when nothing beats the subject.
0.005 USD Coin / request · eip155:8453
POSTx402 · listed
https://x402-trust.com/v1/x402-history
Raw observation history for any publicly listed x402 endpoint: discovery snapshots (listed/delisted/relisted, price changes, payTo changes) and probe time-series (uptime, latency, quoted amount) over the requested window (1-90 days).
0.02 USD Coin / request · eip155:8453
POSTx402 · listed
https://x402-trust.com/v1/x402-trust
Trust score (0-100, grade A-F) for any x402 endpoint -- listed in our catalog or not. Unlike uptime-only checkers, we return ECONOMIC PROOF: the REAL on-chain USDC settlement volume and distinct-payer count for the endpoint's payTo address -- is anyone actually paying it, or is it just live? Computed deterministically from continuous monitoring: 30d probe uptime, 402-envelope spec compliance, latency, observed age, on-chain settlement activity, and advertised-price stability. Includes a full component breakdown, machine-readable flags, and an honest observedDays (we report only the history we actually have, with dataCompleteSince marking our gap-free on-chain coverage). Uncataloged endpoints are live-probed on your first query and auto-adopted into the monitored catalog (first-contact score with low confidence -- history accumulates from there). Each paid call also refreshes the endpoint's free public snapshot (page, badge, card), so a fresh score shows everywhere immediately. Know before you pay.
0.005 USD Coin / request · eip155:8453
POSTx402 · listed
https://x402-trust.com/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.