Paywary

Leaderboard / retry.exende.dev / endpoint

POST https://retry.exende.dev/v1/retries

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 11 probes in the last 7 days.
Category
Utility by llm, confidence 45%
Latest quote
$0.02 on Base to 0x9d25…a3f9
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:40 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
10w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.020x9d25…a3f9defaultyes6h 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
46h agoUtility45%llmv1claude-haiku-5-5: The endpoint executes arbitrary HTTPS requests with retry logic and returns the response of a durable job, which is a generic request relay rather than a clear data category. Utility is the closest fit given its infrastructure-style, non-domain-specific function, though it could also be seen as commerce or other.
2d agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
4h agofree402721 msv2yes$0.020x9d25…a3f9—
11h agofree402384 msv2yes$0.020x9d25…a3f9—
17h agofree402748 msv2yes$0.020x9d25…a3f9—
23h agofree402549 msv2yes$0.020x9d25…a3f9—
30h agofree402493 msv2yes$0.020x9d25…a3f9—
37h agofree402625 msv2yes$0.020x9d25…a3f9—
43h agofree402429 msv2yes$0.020x9d25…a3f9—
2d agofree402610 msv2yes$0.020x9d25…a3f9—
2d agofree402715 msv2yes$0.020x9d25…a3f9—
3d agofree402371 msv2yes$0.020x9d25…a3f9—
3d agofree402727 msv2yes$0.020x9d25…a3f9—