Leaderboard / api.ransomware-tracker.com / endpoint
GET https://api.ransomware-tracker.com/v1/vendor-report
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 11 probes in the last 7 days.
- Category
- Compliance by llm, confidence 60%
- Latest quote
- $3 on Base to 0x2dAF…65dD
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- Observed
- none reported yet (opt-in wrapper telemetry)
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 43m ago
- Next probe
- 2026-11-19 01:35 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $3 | 0x2dAF…65dD | default | yes | 3h ago |
| payai | exact | Base | 0x8335…2913 | $3 | 0x2dAF…65dD | default | yes | 3h 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.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 43h ago | Compliance | 60% | llm | v1 | claude-haiku-5-5: The endpoint produces third-party vendor risk reports from ransomware leak-site claims, aimed at TPRM (third-party risk management) and supplier due diligence. That is closest to compliance screening, though it is threat-intelligence data and could arguably fit signal or dns_domain, so confidence is moderate. |
| 47h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 43m ago | free | 402 | 1141 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 8h ago | free | 402 | 624 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 14h ago | free | 402 | 405 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 20h ago | free | 402 | 542 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 27h ago | free | 402 | 227 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 33h ago | free | 402 | 447 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 40h ago | free | 402 | 396 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 46h ago | free | 402 | 166 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 2d ago | free | 402 | 35 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 2d ago | free | 402 | 546 ms | v2 | yes | $3 | 0x2dAF…65dD | — |
| 3d ago | free | 402 | 520 ms | v2 | yes | $3 | 0x2dAF…65dD | — |