Leaderboard / dev-api.proofestry.dev / endpoint
POST https://dev-api.proofestry.dev/x402/v1/scan/file
Scores measure reliability and honesty, not output quality.
- 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
- 2h ago
- Next probe
- 2026-11-17 16:37 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base Sepolia | 0x036C…CF7e | 10000 | 0x1543…CBEa | default | yes | 6h ago |
| cdp | exact | Solana devnet | 4zMMC9…ncDU | 10000 | 2rpswt…mnFw | default | yes | 6h 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.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 12h ago | Web audit | 35% | llm | v1 | claude-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. |
| 15h ago | Document | 50% | rules | v1 | rule document matched "pdf" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 403 | 201 ms | — | no | — | — | auth_requiredstatus_not_402 |
| 8h ago | free | 403 | 69 ms | — | no | — | — | auth_requiredstatus_not_402 |
| 14h ago | free | 402 | 196 ms | v2 | yes | $0.01 | 0x1543…CBEa | no_base_usdc_optionquotes_testnettestnet_listing |
| 20h ago | free | 402 | 47 ms | v2 | yes | $0.01 | 0x1543…CBEa | no_base_usdc_optionquotes_testnettestnet_listing |
| 27h ago | free | 402 | 46 ms | v2 | yes | $0.01 | 0x1543…CBEa | no_base_usdc_optionquotes_testnettestnet_listing |
| 33h ago | free | 402 | 91 ms | v2 | yes | $0.01 | 0x1543…CBEa | no_base_usdc_optionquotes_testnettestnet_listing |