Leaderboard / api.duoleads.com / endpoint
GET https://api.duoleads.com/v1/geo/pluscode
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
- Utility by llm, confidence 80%
- 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:01 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 | Utility | 80% | llm | v1 | claude-haiku-5-5: Encoding and decoding Open Location Codes (plus codes) from coordinates is a deterministic geospatial conversion akin to geocoding, returning code length, precision and validity. It is not chain, DNS, or data transform in the usual sense, so utility is the closest fit, though data_transform is a plausible alternative given its deterministic nature. |
| 15h ago | Other | 40% | rules | v1 | rule none matched "" in none |
| 22h ago | Utility | 82% | llm | v1 | claude-haiku-5-5: Plus Code encoding and decoding is a deterministic geospatial conversion (coordinates to Open Location Code and back), which fits utility's geocoding-style tools. It is not a chain read, data transform, or public dataset, though data_transform is a plausible alternative since it is a pure encoding. |
| 25h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 91 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 12h ago | free | 402 | 440 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 19h ago | free | 402 | 64 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 25h ago | free | 402 | 246 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 31h ago | free | 402 | 49 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 37h ago | free | 402 | 22 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |
| 44h ago | free | 402 | 28 ms | v2 | yes | $0.05 | 0xCD67…3A39 | — |