Leaderboard / agentshield.live / endpoint
GET https://agentshield.live/aba
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
- Data transform by llm, confidence 60%
- Latest quote
- $0.003 on Base to 0xC87e…25AE
- 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
- 5h ago
- Next probe
- 2026-11-17 23:44 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.003 | 0xC87e…25AE | 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 |
|---|---|---|---|---|---|
| 8h ago | Data transform | 60% | llm | v1 | claude-haiku-5-5: The endpoint validates a US ABA routing number checksum, a deterministic check on input data. It does not confirm the bank or account, so it is not finance_data or compliance. Closest fit is data_transform, with moderate confidence since it is a validation rather than a transform. |
| 25h ago | Data transform | 60% | rules | v1 | rule data_transform matched "checksum" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 161 ms | v2 | yes | $0.003 | 0xC87e…25AE | — |
| 11h ago | free | 402 | 159 ms | v2 | yes | $0.003 | 0xC87e…25AE | — |
| 17h ago | free | 402 | 157 ms | v2 | yes | $0.003 | 0xC87e…25AE | — |
| 23h ago | free | 402 | 151 ms | v2 | yes | $0.003 | 0xC87e…25AE | — |
| 29h ago | free | 402 | 151 ms | v2 | yes | $0.003 | 0xC87e…25AE | — |
| 36h ago | free | 402 | 151 ms | v2 | yes | $0.003 | 0xC87e…25AE | — |
| 42h ago | free | 402 | 151 ms | v2 | yes | $0.003 | 0xC87e…25AE | — |