Paywary

Leaderboard / api.walletforge.app / endpoint

POST https://api.walletforge.app/v1/normalize

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.001 on Base to 0x405b…201c
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
30m ago
Next probe
2026-11-18 03:51 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
payaiexactBase0x8335…2913$0.0010x405b…201cdefaultyes3h 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
2h agoData transform60%llmv1claude-haiku-5-5: The endpoint normalizes raw text and extracts emails, URLs and phones, which is a deterministic text transform rather than a web fetch or model output. Tags suggest scraping and NLP, but the returned output is structured extraction from supplied text, so data_transform fits best.
25h agoWeb scrape60%rulesv1rule web_scrape matched "scraping" in metadata

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
30m agofree402171 msv2yes$0.0010x405b…201c—
7h agofree402271 msv2yes$0.0010x405b…201c—
13h agofree402293 msv2yes$0.0010x405b…201c—
20h agofree402282 msv2yes$0.0010x405b…201c—
27h agofree402209 msv2yes$0.0010x405b…201c—
33h agofree402238 msv2yes$0.0010x405b…201c—
39h agofree402312 msv2yes$0.0010x405b…201c—