Paywary

Leaderboard / toolrail.dev / endpoint

POST https://toolrail.dev/validate/phone

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 1 day ago; new listings earn trust over 30 days.
  • Answered all 7 probes in the last 7 days.
Category
Data transform by llm, confidence 60%
Latest quote
$0.002 on Base to 0xC6E6…8a17
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-17 23:22 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
6w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactSolanaEPjFWd…Dt1v20007zBC8Y…8qCRdefaultyes5m ago
cdpexactBase0x8335…2913$0.0020xC6E6…8a17defaultyes5m 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 agoData transform60%llmv1claude-haiku-5-5: Phone number validation and formatting is a deterministic transform of input text into normalized formats (E.164, national), not a contact enrichment, email, or compliance screen. It could be seen as validation under compliance, but its output is formatting and validity data, so data_transform fits best.
25h agoUtility60%rulesv1rule utility matched "iban" in metadata

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
5h agofree402177 msv2yes$0.0020xC6E6…8a17—
12h agofree402105 msv2yes$0.0020xC6E6…8a17—
18h agofree402188 msv2yes$0.0020xC6E6…8a17—
24h agofree402161 msv2yes$0.0020xC6E6…8a17—
30h agofree40274 msv2yes$0.0020xC6E6…8a17—
37h agofree402173 msv2yes$0.0020xC6E6…8a17—
43h agofree40273 msv2yes$0.0020xC6E6…8a17—