Paywary

Leaderboard / work-1-eanlwuwlwtxnhcqq.prod-runtime.all-hands.dev / endpoint

GET https://work-1-eanlwuwlwtxnhcqq.prod-runtime.all-hands.dev/paid/sanctions-screen

Scores measure reliability and honesty, not output quality.

70Cautionconfidence: medium
  • Responded without asking for payment on 11 probes; it may no longer be an x402 endpoint.
  • Listed only 2 days ago; new listings earn trust over 30 days.
Category
Compliance by llm, confidence 60%
Latest quote
— on — to —
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
48m ago
Next probe
2026-11-19 04:30 UTC

Score components

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

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen

Listing changes

WhenEventFromTo
12h agodisappeared——

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
12h agoCompliance60%llmv1claude-haiku-5-5: The resource path name 'sanctions-screen' suggests sanctions screening, though no description or tags confirm the endpoint's behavior.
12h agoCompliance60%rulesv1rule compliance matched "sanction" in metadata
2d agoWeb audit90%rulesv1rule web_audit matched "phishing" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
48m agofree404173 ms—no——not_foundstatus_not_402
7h agofree404169 ms—no——not_foundstatus_not_402
13h agofree404195 ms—no——not_foundstatus_not_402
19h agofree404182 ms—no——not_foundstatus_not_402
25h agofree40439 ms—no——not_foundstatus_not_402
32h agofree40453 ms—no——not_foundstatus_not_402
38h agofree40453 ms—no——not_foundstatus_not_402
45h agofree40459 ms—no——not_foundstatus_not_402
2d agofree40450 ms—no——not_foundstatus_not_402
2d agofree404287 ms—no——not_foundstatus_not_402
3d agofree40455 ms—no——not_foundstatus_not_402