Paywary

Leaderboard / chain.cyberwarex.com / endpoint

GET https://chain.cyberwarex.com/wallet-check

Scores measure reliability and honesty, not output quality.

57Cautionconfidence: medium
  • Answered 1 of 9 probes in the last 7 days (11%).
  • Answered 1 of 9 probes in the last 30 days (11%).
Category
Other by llm, confidence 30%
Latest quote
— on — to —
Uptime
11% / 7d, 11% / 30d
Delivery
none not yet paid-tested
Observed
none reported yet (opt-in wrapper telemetry)
HTTPS
yes
First listed
2026-11-16
Last probe
5h ago
Next probe
2026-11-18 12:42 UTC

Score components

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

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen

Listing changes

WhenEventFromTo
38h 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
21h agoOther30%llmv1claude-haiku-5-5: The host name suggests chain-related activity and the path 'wallet-check' hints at wallet or on-chain inspection, but there is no description, service name, tags, or example fields to confirm what the endpoint returns, so the classification is low confidence.
38h agoChain read60%rulesv1rule chain_read matched "wallet check" in metadata

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
5h agofree503575 ms—no——server_errorstatus_not_402
12h agofree503617 ms—no——server_errorstatus_not_402
18h agofree503593 ms—no——server_errorstatus_not_402
24h agofree503604 ms—no——server_errorstatus_not_402
31h agofree503648 ms—no——server_errorstatus_not_402
37h agofree503600 ms—no——server_errorstatus_not_402
43h agofree503644 ms—no——server_errorstatus_not_402
2d agofree503556 ms—no——server_errorstatus_not_402
2d agofree402212 msv2yes$0.010x058D…21B2—