Paywary

Leaderboard / api.gadgethumans.com / endpoint

GET https://api.gadgethumans.com/verify-email

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
Email by llm, confidence 93%
Latest quote
$0.01 on Base to 0xe6C3…3A34
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
1h ago
Next probe
2026-11-18 22: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.010xe6C3…3A34defaultyes6h ago
payaiexactSolanaEPjFWd…Dt1v100007RDNyu…Suaudefaultyes6h 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
21h agoEmail93%llmv1claude-haiku-5-5: The endpoint validates an email address for syntax, MX records and disposable-domain signals, which is email validation returning a verdict to the caller. Although it touches DNS (MX lookups), the returned product is email verification, so email is the most specific fit.
44h agoEmail60%rulesv1rule email matched "verify an email" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
1h agofree402190 msv2yes$0.010xe6C3…3A34—
7h agofree40295 msv2yes$0.010xe6C3…3A34—
13h agofree40262 msv2yes$0.010xe6C3…3A34—
20h agofree402231 msv2yes$0.010xe6C3…3A34—
26h agofree40252 msv2yes$0.010xe6C3…3A34—
32h agofree40225 msv2yes$0.010xe6C3…3A34—
39h agofree40250 msv2yes$0.010xe6C3…3A34—
46h agofree40260 msv2yes$0.010xe6C3…3A34—
2d agofree40241 msv2yes$0.010xe6C3…3A34—
2d agofree40241 msv2yes$0.010xe6C3…3A34—