Paywary

Leaderboard / chainverdict.xyz / endpoint

GET https://chainverdict.xyz/v1/validate/lei/:lei

Scores measure reliability and honesty, not output quality.

70Cautionconfidence: medium
  • Responded without asking for payment on 7 probes; it may no longer be an x402 endpoint.
  • Listed only 1 day 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
HTTPS
yes
First listed
2026-11-16
Last probe
3h ago
Next probe
2026-11-17 23:59 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
6w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0020xAe26…1842defaultyes1h 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
7h agoCompliance60%llmv1claude-haiku-5-5: Validates a Legal Entity Identifier (a financial regulatory identifier) structurally per ISO 17442. It is a compliance-style validation rather than enrichment, since it does not look up the registry. The host name suggests a verdict service, but the description is clear about the function, so confidence is moderate rather than high; data_transform was considered since it is purely structural, but the regulatory identifier context points to compliance.
23h agoEnrichment60%rulesv1rule enrichment matched "legal entity" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
3h agofree400187 ms—no——unexpected_status:400status_not_402
10h agofree400245 ms—no——unexpected_status:400status_not_402
16h agofree400226 ms—no——unexpected_status:400status_not_402
22h agofree400224 ms—no——unexpected_status:400status_not_402
28h agofree400198 ms—no——unexpected_status:400status_not_402
34h agofree400167 ms—no——unexpected_status:400status_not_402
40h agofree400189 ms—no——unexpected_status:400status_not_402