Paywary

Leaderboard / public-domain-check-production.up.railway.app / endpoint

GET https://public-domain-check-production.up.railway.app/v1/sanctions/screen

Scores measure reliability and honesty, not output quality.

75Payconfidence: medium
  • Quoted a price different from the listed price on 9 of 9 comparable probes.
  • Listed only 2 days ago; new listings earn trust over 30 days.
Category
Compliance by rules, confidence 90%
Latest quote
$0.003 on Base to 0x13B6…4F0B
Uptime
100% / 7d, 100% / 30d
Delivery
none not yet paid-tested
Observed
none reported yet (opt-in wrapper telemetry)
HTTPS
yes
First listed
2026-11-16
Last probe
1h ago
Next probe
2026-11-18 12:52 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
100w 15%
Price honesty
0w 15%
Delivery after payment
n/aexcluded
Wallet stability
100w 10%
Listing age
7w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.010x13B6…4F0Bdefaultyes3h ago

Paid probes

No paid probes yet. Paid probing is off by default and runs weekly per host under a strict spend cap; each paid probe links to its on-chain transaction here.

Delivery checks

Inside each paid probe we ask for something whose correct answer we know, then compare. A pass means the seller delivered what it was paid for; a fail means it charged and returned something wrong; inconclusive means we could not judge (no reference, unknown input shape, or a non-2xx response). Every row carries the request, the response hash and the reference so the verdict can be reproduced. Judged results feed the "Delivery after payment" component (pass 1, error after payment 0.25, fail 0); inconclusive rows are excluded; a fail in the last 14 days caps the verdict at caution. Methodology.

No delivery checks yet. They run inside the weekly paid probe.

Classification history

Every classification is kept; the newest row is the current category. Rules match the listing text; the model is consulted only when the rules are unsure.

WhenCategoryConfidenceMethodVersionEvidence
35h agoCompliance90%rulesv1rule compliance matched "ofac" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
1h agofree402105 msv2yes$0.0030x13B6…4F0Bprice_below_listingprice_mismatch
8h agofree402124 msv2yes$0.0030x13B6…4F0Bprice_below_listingprice_mismatch
14h agofree40293 msv2yes$0.0030x13B6…4F0Bprice_below_listingprice_mismatch
21h agofree402143 msv2yes$0.0030x13B6…4F0Bprice_below_listingprice_mismatch
27h agofree402135 msv2yes$0.0030x13B6…4F0Bprice_below_listingprice_mismatch
33h agofree402116 msv2yes$0.0030x13B6…4F0Bprice_below_listingprice_mismatch
39h agofree402108 msv2yes$0.0030x13B6…4F0Bprice_below_listingprice_mismatch
46h agofree402110 msv2yes$0.0030x13B6…4F0Bprice_below_listingprice_mismatch
2d agofree40281 msv2yes$0.0030x13B6…4F0Bprice_below_listingprice_mismatch