Paywary

Leaderboard / twin.unykorn.org / endpoint

POST https://twin.unykorn.org/research/npm-package

Scores measure reliability and honesty, not output quality.

79Payconfidence: medium
  • Answered 6 of 7 probes in the last 7 days (86%).
  • Answered 6 of 7 probes in the last 30 days (86%).
Category
Web audit by llm, confidence 50%
Latest quote
$0.003 on Base to 0x7d9a…56DB
Uptime
86% / 7d, 86% / 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-18 03:55 UTC

Score components

Uptime, 7 days
60w 15%
Uptime, 30 days
60w 15%
Valid x402 challenge
100w 15%
Price honesty
100w 15%
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.0030x7d9a…56DBdefaultyes3h ago
cdpexactPolygon0x3c49…335930000x7d9a…56DBdefaultyes3h ago
cdpexactSolanaEPjFWd…Dt1v300052EqTZ…ZFQpdefaultyes3h 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
5h agoWeb audit50%llmv1claude-haiku-5-5: The endpoint returns npm package facts (version, license, deps, deprecation) for a package, which is closest to a dependency/supply-chain audit. It is not a clean fit: the listing is about package metadata rather than a URL audit, and 'dependency check' tags could also suggest other categories, so confidence is moderate.
28h agoPublic data60%rulesv1rule public_data matched "npm package" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
4h agofree402164 msv2yes$0.0030x7d9a…56DB—
10h agofree402112 msv2yes$0.0030x7d9a…56DB—
16h agofree402101 msv2yes$0.0030x7d9a…56DB—
23h agofree402128 msv2yes$0.0030x7d9a…56DB—
30h agofree502141 ms—no——server_errorstatus_not_402
36h agofree402208 msv2yes$0.0030x7d9a…56DB—
43h agofree40290 msv2yes$0.0030x7d9a…56DB—