Paywary

Leaderboard / dev-api.proofestry.dev / endpoint

POST https://dev-api.proofestry.dev/x402/v1/scan/file

Scores measure reliability and honesty, not output quality.

89Payconfidence: medium
  • 2 probes got a response that was not a 402 payment challenge.
  • Listed only 1 day ago; new listings earn trust over 30 days.
Category
Web audit by llm, confidence 35%
Latest quote
— on — to —
Uptime
100% / 7d, 100% / 30d
HTTPS
yes
First listed
2026-11-16
Last probe
5h ago
Next probe
2026-11-17 16:37 UTC

Score components

Uptime, 7 days
100w 20%
Uptime, 30 days
100w 15%
Valid x402 challenge
67w 15%
Price honesty
100w 15%
Delivery after payment
n/aexcluded
Wallet stability
100w 10%
Listing age
5w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase Sepolia0x036C…CF7e100000x1543…CBEadefaultyes2h ago
cdpexactSolana devnet4zMMC9…ncDU100002rpswt…mnFwdefaultyes2h 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. Delivery results do not affect scores yet.

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
14h agoWeb audit35%llmv1claude-haiku-5-5: The endpoint scans an uploaded file for hidden content, active content and prompt-injection text, which is security analysis of a supplied artifact. None of the categories match a file security scanner well. web_audit is the closest fit for security scanning of a supplied item, though it is designed for URLs, so confidence is moderate-low. document is another possible fit since the input is a PDF-style file, but the output is a security verdict rather than document conversion or extraction.
18h agoDocument50%rulesv1rule document matched "pdf" in metadata

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
5h agofree403201 ms—no——auth_requiredstatus_not_402
11h agofree40369 ms—no——auth_requiredstatus_not_402
17h agofree402196 msv2yes$0.010x1543…CBEano_base_usdc_optionquotes_testnettestnet_listing
23h agofree40247 msv2yes$0.010x1543…CBEano_base_usdc_optionquotes_testnettestnet_listing
30h agofree40246 msv2yes$0.010x1543…CBEano_base_usdc_optionquotes_testnettestnet_listing
36h agofree40291 msv2yes$0.010x1543…CBEano_base_usdc_optionquotes_testnettestnet_listing