Leaderboard / api.glianalabs.com / endpoint
POST https://api.glianalabs.com/x402/tools/contract-scan
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
- Web audit by llm, confidence 30%
- Latest quote
- $0.004 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:19 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.004 | 0x7662…80AD | default | yes | 1h ago |
| cdp | upto | Base | 0x8335…2913 | $0.004 | 0x7662…80AD | permit2 | yes | 1h ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 4000 | CXSdm7…3Ygh | default | yes | 1h 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 |
|---|---|---|---|---|---|
| 53m ago | Web audit | 30% | llm | v1 | claude-haiku-5-5: The endpoint scans a deployed contract's bytecode for risks to users, taking chain and address inputs. Closest fit is crypto_market token safety, but no category clearly covers contract bytecode risk analysis; the description is partly generic boilerplate, so confidence is modest. Chain_read is possible since it reads on-chain data, but the output is a risk assessment rather than raw chain data. |
| 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 | 59 ms | v2 | yes | $0.004 | 0x7662…80AD | — |
| 10h ago | free | 402 | 40 ms | v2 | yes | $0.004 | 0x7662…80AD | — |
| 16h ago | free | 402 | 247 ms | v2 | yes | $0.004 | 0x7662…80AD | — |
| 22h ago | free | 402 | 29 ms | v2 | yes | $0.004 | 0x7662…80AD | — |
| 28h ago | free | 402 | 226 ms | v2 | yes | $0.004 | 0x7662…80AD | — |
| 35h ago | free | 402 | 30 ms | v2 | yes | $0.004 | 0x7662…80AD | — |