Paywary

Leaderboard / api.duoleads.com / endpoint

GET https://api.duoleads.com/v1/code/url

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
Data transform by llm, confidence 72%
Latest quote
$0.05 on Base to 0xCD67…3A39
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 18:19 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
payaiexactBase0x8335…2913$0.050xCD67…3A39defaultyes6h ago

Listing changes

WhenEventFromTo
34h 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
34h agoData transform72%llmv1claude-haiku-5-5: The endpoint deterministically parses and canonicalises a URL, normalising components and returning structured fields, which fits a deterministic transform. It also extracts the registrable domain via the Public Suffix List, which could arguably fall under dns_domain, but the core output is URL parsing and normalisation rather than DNS or IP intelligence.
34h agoOther40%rulesv1rule none matched "" in none
41h agoData transform80%llmv1claude-haiku-5-5: The endpoint parses and canonicalises a URL and extracts components deterministically, which fits a deterministic transform tool. It is not DNS or WHOIS lookup, though the registrable domain via the Public Suffix List is close to dns_domain, so confidence is moderate.
44h agoData transform60%rulesv1rule data_transform matched "url parse" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
5h agofree40234 msv2yes$0.050xCD67…3A39—
12h agofree40231 msv2yes$0.050xCD67…3A39—
18h agofree402102 msv2yes$0.050xCD67…3A39—
25h agofree402173 msv2yes$0.050xCD67…3A39—
31h agofree402246 msv2yes$0.050xCD67…3A39—
37h agofree4021257 msv2yes$0.050xCD67…3A39—
43h agofree40278 msv2yes$0.050xCD67…3A39—
2d agofree40276 msv2yes$0.050xCD67…3A39—
2d agofree40238 msv2yes$0.050xCD67…3A39—
3d agofree40238 msv2yes$0.050xCD67…3A39—