Leaderboard / api.agentstools.dev / endpoint
GET https://api.agentstools.dev/geocode/reverse
Scores measure reliability and honesty, not output quality.
- Answered 8 of 9 probes in the last 7 days (89%).
- Answered 8 of 9 probes in the last 30 days (89%).
- Category
- Utility by llm, confidence 80%
- Latest quote
- $0.002 on Base to 0xF22e…f493
- Uptime
- 89% / 7d, 89% / 30d
- Delivery
- none not yet paid-tested
- Observed
- none reported yet (opt-in wrapper telemetry)
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 5h ago
- Next probe
- 2026-11-18 18:09 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.002 | 0xF22e…f493 | 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. 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 |
|---|---|---|---|---|---|
| 33h ago | Utility | 80% | llm | v1 | claude-haiku-5-5: Reverse geocoding converts coordinates to a street address via OpenStreetMap, which matches the utility category's geocoding examples. The NWS enrichment for US points is secondary, so the primary category is utility rather than public_data. |
| 43h ago | Enrichment | 60% | rules | v1 | rule enrichment matched "enrich" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 571 ms | v2 | yes | $0.002 | 0xF22e…f493 | — |
| 11h ago | free | 402 | 584 ms | v2 | yes | $0.002 | 0xF22e…f493 | — |
| 18h ago | free | 402 | 588 ms | v2 | yes | $0.002 | 0xF22e…f493 | — |
| 24h ago | free | 402 | 620 ms | v2 | yes | $0.002 | 0xF22e…f493 | — |
| 31h ago | free | 402 | 564 ms | v2 | yes | $0.002 | 0xF22e…f493 | — |
| 37h ago | free | 402 | 582 ms | v2 | yes | $0.002 | 0xF22e…f493 | — |
| 43h ago | free | 402 | 539 ms | v2 | yes | $0.002 | 0xF22e…f493 | — |
| 2d ago | free | network | 10244 ms | — | — | — | — | no_responsefetch_error:network |
| 3d ago | free | 402 | 181 ms | v2 | yes | $0.002 | 0xF22e…f493 | — |