Paywary

Leaderboard / api.powerstripsecurity.workers.dev / endpoint

POST https://api.powerstripsecurity.workers.dev/v1/scan

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
Other by llm, confidence 45%
Latest quote
$0.002 on Base to 0xa8d3…a808
Uptime
100% / 7d, 100% / 30d
Delivery
none not yet paid-tested
HTTPS
yes
First listed
2026-11-16
Last probe
5h ago
Next probe
2026-11-17 23:05 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.0020xa8d3…a808defaultyes3h 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 agoOther45%llmv1claude-haiku-5-5: This is a prompt-injection scanner for agent content, which is a security/content-safety tool. None of the listed categories fit cleanly: it is not web_audit (it audits content, not a site URL supplied by the caller), not compliance, and not inference. The closest fit is web_audit or other, and since it does not audit a URL, 'other' is the most accurate choice with moderate confidence.
24h agoDocument60%rulesv1rule document matched "scanned" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
5h agofree4023223 msv2yes$0.0020xa8d3…a808—
11h agofree402385 msv2yes$0.0020xa8d3…a808—
18h agofree402353 msv2yes$0.0020xa8d3…a808—
24h agofree402518 msv2yes$0.0020xa8d3…a808—
30h agofree402296 msv2yes$0.0020xa8d3…a808—
36h agofree402447 msv2yes$0.0020xa8d3…a808—
43h agofree402525 msv2yes$0.0020xa8d3…a808—