Leaderboard / api.agent-data.workers.dev / endpoint
GET https://api.agent-data.workers.dev/api/v1/security/epss
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Web audit by llm, confidence 35%
- Latest quote
- $0.01 on Base to 0x2a99…bd4e
- Uptime
- 100% / 7d, 100% / 30d
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 27m ago
- Next probe
- 2026-11-17 23:19 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Solana | Es9vMF…wNYB | 10000 | EQuJg7…HKFA | default | yes | 4h ago |
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0x2a99…bd4e | default | yes | 4h ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 10000 | EQuJg7…HKFA | default | yes | 4h 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 |
|---|---|---|---|---|---|
| 10h ago | Web audit | 35% | llm | v1 | claude-haiku-5-5: EPSS returns exploit probability scores for CVEs, which is security vulnerability data. None of the categories cover CVE scoring directly; web_audit is the closest security-oriented fit, though it targets URLs the caller supplies, so confidence is modest. public_data and other were considered but the security focus points toward web_audit. |
| 20h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 27m ago | free | 402 | 37 ms | v2 | yes | $0.01 | 0x2a99…bd4e | — |
| 7h ago | free | 402 | 36 ms | v2 | yes | $0.01 | 0x2a99…bd4e | — |
| 13h ago | free | 402 | 14 ms | v2 | yes | $0.01 | 0x2a99…bd4e | — |
| 19h ago | free | 402 | 49 ms | v2 | yes | $0.01 | 0x2a99…bd4e | — |
| 25h ago | free | 402 | 38 ms | v2 | yes | $0.01 | 0x2a99…bd4e | — |
| 32h ago | free | 402 | 191 ms | v2 | yes | $0.01 | 0x2a99…bd4e | — |
| 38h ago | free | 402 | 53 ms | v2 | yes | $0.01 | 0x2a99…bd4e | — |