Leaderboard / api.duoleads.com / endpoint
GET https://api.duoleads.com/v1/id/national
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
- Compliance by llm, confidence 60%
- Latest quote
- $0.05 on Base to 0xCD67…3A39
- 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
- 6h ago
- Next probe
- 2026-11-17 23:11 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| payai | exact | Base | 0x8335…2913 | $0.05 | 0xCD67…3A39 | default | yes | 15m ago |
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 16h ago | disappeared | — | — |
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 |
|---|---|---|---|---|---|
| 15h ago | Compliance | 60% | llm | v1 | claude-haiku-5-5: Validates national identity, tax and company registration numbers against official checksum rules across 23 countries, which is closest to compliance checks (KYC-style validation), though it is also deterministic validation that could fit data_transform. |
| 15h ago | Enrichment | 60% | rules | v1 | rule enrichment matched "company registration" in description |
| 22h ago | Compliance | 72% | llm | v1 | claude-haiku-5-5: The endpoint validates VAT, tax and national ID numbers against country checksum rules, which is closest to compliance tooling for tax identifiers. It does not perform registry lookups, so it is not enrichment or public_data, and it is not a pure deterministic transform despite using checksums. |
| 25h ago | Enrichment | 60% | rules | v1 | rule enrichment matched "company registration" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 735 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 12h ago | free | 402 | 53 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 19h ago | free | 402 | 138 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 25h ago | free | 402 | 57 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 31h ago | free | 402 | 150 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 37h ago | free | 402 | 28 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 44h ago | free | 402 | 15 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |