Paywary

Leaderboard / openverbs.com / endpoint

POST https://openverbs.com/api/phone/v1/parse

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 0xb3f4…194A
Uptime
100% / 7d, 100% / 30d
Delivery
none not yet paid-tested
HTTPS
yes
First listed
2026-11-16
Last probe
2h ago
Next probe
2026-11-17 23:01 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
cdpexactBase0x8335…2913$0.0020xb3f4…194Adefaultyes21s 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
18h agoData transform60%llmv1claude-haiku-5-5: The endpoint parses, validates and formats phone numbers into E.164, national, international or RFC 3966 representations. It is a deterministic syntactic transform with no carrier lookup, so data_transform fits best, though it could arguably be seen as utility or enrichment.
22h agoEnrichment50%rulesv1rule enrichment matched "phone number lookup" in metadata

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
2h agofree402238 msv2yes$0.0020xb3f4…194A—
9h agofree402139 msv2yes$0.0020xb3f4…194A—
15h agofree402156 msv2yes$0.0020xb3f4…194A—
21h agofree40299 msv2yes$0.0020xb3f4…194A—
27h agofree402153 msv2yes$0.0020xb3f4…194A—
34h agofree402112 msv2yes$0.0020xb3f4…194A—
40h agofree402115 msv2yes$0.0020xb3f4…194A—