Paywary

Leaderboard / oracle.cyberwarex.com / endpoint

GET https://oracle.cyberwarex.com/v1/holders/scan

Scores measure reliability and honesty, not output quality.

88Payconfidence: medium
  • 4 probes got a response that was not a 402 payment challenge.
  • Listed only 2 days ago; new listings earn trust over 30 days.
Category
Other by llm, confidence 20%
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
4h ago
Next probe
2026-11-19 01:08 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
64w 15%
Price honesty
100w 15%
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 agoOther20%llmv1claude-haiku-5-5: Path suggests token holder scanning, but no description, tags, or examples are provided to confirm the endpoint's purpose.
12h agoOther20%rulesv1rule none matched "" in none
46h agoCrypto market data60%llmv1claude-haiku-5-5: Profiles token holders on several chains for sniper, bundle and sybil activity, producing a risk score and verdict. This is token safety analysis, which maps to crypto_market, though it could arguably be a signal since it outputs a risk verdict.
2d agoFinance data60%rulesv1rule finance_data matched "robinhood" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
4h agofree410674 ms—no——not_foundstatus_not_402
11h agofree410182 ms—no——not_foundstatus_not_402
17h agofree410566 ms—no——not_foundstatus_not_402
24h agofree410575 ms—no——not_foundstatus_not_402
30h agofree402213 msv2yes$10x058D…21B2—
37h agofree402554 msv2yes$10x058D…21B2—
43h agofree402640 msv2yes$10x058D…21B2—
2d agofree402303 msv2yes$10x058D…21B2—
2d agofree402186 msv2yes$10x058D…21B2—
3d agofree402213 msv2yes$10x058D…21B2—
3d agofree402190 msv2yes$10x058D…21B2—