Endpoint

B

trust402.vercel.app/api/trust/check-x402

· score 77/100 · recomputed 49m ago

Run a fast live probe for one x402 endpoint and summarize challenge/payment-flow readiness.

NEW_UNKNOWN
First seen
5d ago
Probes stored
3

Score

B
77 of 100
recomputed 49m ago

The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.

We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.

Recent probes

WhenCodeLatencyScheme and network RecipientPriceFindings
5h ago 402 135 ms exact
eip155:8453
0x3f4C…049B 0.005000 clean
4d ago 402 294 ms exact
eip155:8453
0x3f4C…049B 0.005000 clean
4d ago 402 161 ms exact
eip155:8453
0x3f4C…049B 0.005000 clean

Reference

URLhttps://trust402.vercel.app/api/trust/check-x402
Sourcesbazaar
Recipient per catalogue0x3f4CEE4c6bad04FcCA3138dFFDEE579ddf17049B
Price per catalogue0.005000
Machine access/v1/endpoint · /full · badge

Is this your endpoint?

The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.

We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.

Next

Market overview →

Payments, median ticket, who pays whom, who settles.

Wallets →

Payers, recipients and facilitators, listed separately.

Facilitators →

Who actually settles — including those in no public registry.

API →

Verdict before payment, seller and wallet scores, market aggregates.