Paywary

Leaderboard / netintel.dev / endpoint

GET https://netintel.dev/lead/check

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 60%
Latest quote
$0.005 on Base to 0xdaDc…b9Df
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-18 18:34 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
8w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0050xdaDc…b9Dfdefaultyes5h ago
cdpexactSolanaEPjFWd…Dt1v50008FVeyb…Gr5sdefaultyes5h 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
33h agoEmail60%llmv1claude-haiku-5-5: The endpoint verifies a sales lead's email address (syntax, MX, disposable/role checks) and returns a yes/risky/no outreach verdict. It is email validation, though it also runs DNS-level checks on the company domain, so enrichment or dns_domain could be argued. Email is the closest fit for what the caller receives.
42h agoEmail60%rulesv1rule email matched "verifies the email" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
4h agofree40210 msv2yes$0.0050xdaDc…b9Df—
10h agofree40231 msv2yes$0.0050xdaDc…b9Df—
16h agofree40230 msv2yes$0.0050xdaDc…b9Df—
23h agofree40223 msv2yes$0.0050xdaDc…b9Df—
29h agofree40213 msv2yes$0.0050xdaDc…b9Df—
35h agofree40273 msv2yes$0.0050xdaDc…b9Df—
42h agofree40238 msv2yes$0.0050xdaDc…b9Df—
2d agofree40215 msv2yes$0.0050xdaDc…b9Df—
2d agofree40212 msv2yes$0.0050xdaDc…b9Df—
3d agofree402308 msv2yes$0.0050xdaDc…b9Df—