Paywary

Leaderboard / api.gadgethumans.com / endpoint

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

Scores measure reliability and honesty, not output quality.

84Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered 9 of 10 probes in the last 7 days (90%).
Category
Email by llm, confidence 93%
Latest quote
— on — to —
Uptime
90% / 7d, 90% / 30d
Delivery
none not yet paid-tested
Observed
none reported yet (opt-in wrapper telemetry)
HTTPS
yes
First listed
2026-11-16
Last probe
59m ago
Next probe
2026-11-19 04:13 UTC

Score components

Uptime, 7 days
72w 15%
Uptime, 30 days
72w 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.0020xe6C3…3A34defaultyes6h 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 deliverability, returning a verdict. This is email validation, which maps to the email category rather than dns_domain, even though it performs MX lookups.
43h agoEmail60%rulesv1rule email matched "check if an email" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
59m agofreenetwork3172 ms————no_responsefetch_error:network
7h agofree40268 msv2yes$0.0020xe6C3…3A34—
13h agofree40289 msv2yes$0.0020xe6C3…3A34—
19h agofree40287 msv2yes$0.0020xe6C3…3A34—
25h agofree40239 msv2yes$0.0020xe6C3…3A34—
32h agofree40230 msv2yes$0.0020xe6C3…3A34—
39h agofree40246 msv2yes$0.0020xe6C3…3A34—
46h agofree402161 msv2yes$0.0020xe6C3…3A34—
2d agofree40240 msv2yes$0.0020xe6C3…3A34—
2d agofree40246 msv2yes$0.0020xe6C3…3A34—