Paywary

Leaderboard / paket.halowerk.com / endpoint

POST https://paket.halowerk.com/v1/npm-publish-path-boundaries

Scores measure reliability and honesty, not output quality.

—Unverifiedconfidence: none
  • Not probed yet. Listed endpoints are probed within six hours of discovery.
Category
Other by rules, confidence 40%
Latest quote
— on — to —
Uptime
— / 7d, — / 30d
Delivery
none not yet paid-tested
HTTPS
yes
First listed
2026-11-17
Last probe
never
Next probe
2026-11-17 19:36 UTC

Score components

No score yet.

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0050x2880…4E5Eeip3009yes24m 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
14m agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags