Paywary

Leaderboard / datenvertrag.halowerk.com / endpoint

POST https://datenvertrag.halowerk.com/v1/transaction-fragment-rank-audit

Scores measure reliability and honesty, not output quality.

94Payconfidence: high
  • Listed only 3 days ago; new listings earn trust over 30 days.
  • Answered all 13 probes in the last 7 days.
Category
Data transform by llm, confidence 45%
Latest quote
$0.003 on Base to 0x2880…4E5E
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-19 16:55 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
12w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0030x2880…4E5Eeip3009yes2h ago

Listing changes

WhenEventFromTo
2d agoreappearedfalsetrue
3d agodisappeared——

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
42h agoData transform45%llmv1claude-haiku-5-5: The endpoint validates a caller-supplied CDC transaction fragment set by checking END event counts and ordinal positions, which is a deterministic structural check on supplied data rather than any chain, market, or web lookup. It is not clearly a generic JSON tool, so confidence is moderate; the description is dense and somewhat jargon-heavy, so 'other' was considered but the deterministic transform fits best.
2d agoOther40%rulesv1rule none matched "" in none
3d agoOther20%rulesv1rule none matched "" in none
3d agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
4h agofree402469 msv2yes$0.0030x2880…4E5E—
10h agofree402459 msv2yes$0.0030x2880…4E5E—
16h agofree402449 msv2yes$0.0030x2880…4E5E—
22h agofree402460 msv2yes$0.0030x2880…4E5E—
28h agofree402472 msv2yes$0.0030x2880…4E5E—
34h agofree402453 msv2yes$0.0030x2880…4E5E—
40h agofree402527 msv2yes$0.0030x2880…4E5E—
47h agofree402164 msv2yes$0.0030x2880…4E5E—
2d agofree402498 msv2yes$0.0030x2880…4E5E—
3d agofree402576 msv2yes$0.0030x2880…4E5E—
3d agofree402466 msv2yes$0.0030x2880…4E5E—
3d agofree402155 msv2yes$0.0030x2880…4E5E—
3d agofree402153 msv2yes$0.0030x2880…4E5E—