Paywary

Leaderboard / api.x402node.dev / endpoint

GET https://api.x402node.dev/password/strength

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 10 probes in the last 7 days.
Category
Utility by llm, confidence 60%
Latest quote
$0.0022 on Base to 0x4466…125e
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
11m ago
Next probe
2026-11-19 04:30 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
100w 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
payaiexactSolanaEPjFWd…Dt1v22009urRvU…o1updefaultyes5h ago
cdpexactBase0x8335…2913$0.00220x4466…125edefaultyes5h ago
cdpexactSolanaEPjFWd…Dt1v22009urRvU…o1updefaultyes5h ago

Listing changes

WhenEventFromTo
24h agoreappearedfalsetrue
24h agoreappearedfalsetrue
27h agodisappeared——
27h 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
24h agoUtility60%llmv1claude-haiku-5-5: Password strength estimation is a small deterministic utility returning score and crack time; no existing category fits precisely.
24h agoOther40%rulesv1rule none matched "" in none
27h agoOther30%llmv1claude-haiku-5-5: The endpoint path suggests a password strength checker, which would be a data_transform or utility style check, but no description, service name, or tags are provided, so the listing alone says too little to classify it with confidence.
27h agoOther20%rulesv1rule none matched "" in none
2d agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
11m agofree40289 msv2yes$0.00220x4466…125e—
6h agofree40226 msv2yes$0.00220x4466…125e—
13h agofree40225 msv2yes$0.00220x4466…125e—
19h agofree40227 msv2yes$0.00220x4466…125e—
25h agofree40224 msv2yes$0.00220x4466…125elisted_option_not_quoted
31h agofree40256 msv2yes$0.00220x4466…125e—
38h agofree40267 msv2yes$0.00220x4466…125e—
44h agofree40272 msv2yes$0.00220x4466…125e—
2d agofree40275 msv2yes$0.00220x4466…125e—
2d agofree40249 msv2yes$0.00220x4466…125e—
3d agofree40251 msv2yes$0.00220x4466…125e—