Paywary

Leaderboard / x402.pkgproof.net / endpoint

POST https://x402.pkgproof.net/v1/verify

Scores measure reliability and honesty, not output quality.

84Payconfidence: medium
  • 5 probes got a response that was not a 402 payment challenge.
  • Listed only 2 days ago; new listings earn trust over 30 days.
Category
Web audit by llm, confidence 50%
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
5h ago
Next probe
2026-11-18 11:57 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
44w 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
cdpexactBase0x8335…2913$0.050xB1fe…b98Edefaultyes6h 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
34h agoWeb audit50%llmv1claude-haiku-5-5: The endpoint audits a supply-chain artifact, an npm or PyPI package, for security risks such as advisories, install scripts, typosquatting and provenance, returning a safe/caution/block verdict. That is closest to a security audit, though it audits packages rather than a URL the caller supplies, so it is not a clean fit. Confidence is moderate.
37h agoPublic data60%rulesv1rule public_data matched "pypi" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
5h agofree2001190 ms—no——no_payment_requiredstatus_not_402
11h agofree2001247 ms—no——no_payment_requiredstatus_not_402
18h agofree4021462 msv2yes$0.050xB1fe…b98E—
24h agofree402963 msv2yes$0.050xB1fe…b98E—
30h agofree200855 ms—no——no_payment_requiredstatus_not_402
36h agofree2001288 ms—no——no_payment_requiredstatus_not_402
42h agofree402900 msv2yes$0.050xB1fe…b98E—
2d agofree402830 msv2yes$0.050xB1fe…b98E—
2d agofree2001256 ms—no——no_payment_requiredstatus_not_402