Leaderboard / api.glianalabs.com / endpoint
POST https://api.glianalabs.com/x402/tools/calldata-decode
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 6 probes in the last 7 days.
- Category
- Chain read by llm, confidence 60%
- Latest quote
- $0.002 on Base to 0x7662…80AD
- Uptime
- 100% / 7d, 100% / 30d
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 4h ago
- Next probe
- 2026-11-17 17:44 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.002 | 0x7662…80AD | default | yes | 2h ago |
| cdp | upto | Base | 0x8335…2913 | $0.002 | 0x7662…80AD | permit2 | yes | 2h ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 2000 | CXSdm7…3Ygh | default | yes | 2h 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. Delivery results do not affect scores yet.
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 |
|---|---|---|---|---|---|
| 1h ago | Chain read | 60% | llm | v1 | claude-haiku-5-5: The endpoint decodes transaction calldata to explain what a transaction does before signing, which is closest to on-chain data interpretation. It could also fit data_transform since it is a deterministic decode, but its purpose is tied to public chain transactions, so chain_read is the best match. |
| 18h ago | Finance data | 60% | rules | v1 | rule finance_data matched "sec filing" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 608 ms | v2 | yes | $0.002 | 0x7662…80AD | — |
| 10h ago | free | 402 | 157 ms | v2 | yes | $0.002 | 0x7662…80AD | — |
| 16h ago | free | 402 | 291 ms | v2 | yes | $0.002 | 0x7662…80AD | — |
| 22h ago | free | 402 | 523 ms | v2 | yes | $0.002 | 0x7662…80AD | — |
| 29h ago | free | 402 | 480 ms | v2 | yes | $0.002 | 0x7662…80AD | — |
| 35h ago | free | 402 | 211 ms | v2 | yes | $0.002 | 0x7662…80AD | — |