Endpoint

B

x402.payperbyte.io/feeds/merchant-screen

Merchant Screen Oracle · score 77/100 · recomputed 10m ago

Know-Your-Agent (KYA) counterparty screening — merchant pillar. Pre-settlement merchant screen: signed ALLOW/WARN/BLOCK on a (domain, payTo, observed price) BEFORE an agent settles an x402 payment. ms-v1 ruleset over first-party signals measured at query time — RDAP domain age, live TLS handshake (cert age, issuer, SAN match), off-domain redirect probe, brand-similarity distance vs a committed known-brand corpus, and the merchant's own advertised x402 manifest price. Method disclosed per field; unmeasurable signals report unverified and only lower confidence. The verdict carries an embedded EIP-712 PayloadAttestation — recompute keccak256(answer) and recover the signer before acting. Trust boundary: the payTo and price are values you assert, not values we observe on your payment — the verdict is a point-in-time snapshot of the exact tuple you supplied, and it neither sees nor constrains the address you ultimately settle to. Before releasing funds compare answer.query against the 402 challenge you are about to pay (answer.query.address is lowercased — compare case-insensitively). The receipt proves provenance and integrity, not correctness. Every query is logged and retained: the domain, the payTo address and price you supplied, the verdict, and a summary of the signals behind it. Producing a verdict requires live outbound requests against the screened domain itself — the merchant may observe this traffic; screening is not covert.

NEW_UNKNOWN
First seen
5d ago
Probes stored
4

Score

B
77 of 100
recomputed 10m 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
3h ago 402 162 ms exact
eip155:8453
0xffFf…E0DB 0.100000 clean
10h ago 402 400 ms exact
eip155:8453
0xffFf…E0DB 0.100000 clean
4d ago 402 374 ms exact
eip155:8453
0xffFf…E0DB 0.100000 clean
4d ago 402 344 ms exact
eip155:8453
0xffFf…E0DB 0.100000 clean

Reference

URLhttps://x402.payperbyte.io/feeds/merchant-screen
Sourcesbazaar well-known
Recipient per catalogue0xffFf4B8Da8C165B556326453446F6940C8AFE0DB
Price per catalogueNaN
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.