Leaderboard / apkcube.com / endpoint
GET https://apkcube.com/api/v1/lookup/hash/:hash
Scores measure reliability and honesty, not output quality.
- Responded without asking for payment on 6 probes; it may no longer be an x402 endpoint.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Category
- DNS and domains by llm, confidence 50%
- Latest quote
- — on — to —
- Uptime
- 100% / 7d, 100% / 30d
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 6h ago
- Next probe
- 2026-11-17 16:53 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.05 | 0xaf4e…9c09 | default | yes | 3h ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 50000 | GXEo7n…4Apj | 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. 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 |
|---|---|---|---|---|---|
| 10h ago | DNS and domains | 50% | llm | v1 | claude-haiku-5-5: The endpoint takes an MD5, SHA-1 or SHA-256 hash and returns the Android app, version and build it belongs to, which is threat-intel style identification. None of the listed categories is a perfect fit; dns_domain covers threat-intel and IP/domain intelligence most closely, but data_transform or other could also apply, so confidence is moderate. |
| 19h ago | Data transform | 60% | rules | v1 | rule data_transform matched "hash" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 400 | 55 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 12h ago | free | 400 | 149 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 19h ago | free | 400 | 171 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 25h ago | free | 400 | 138 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 31h ago | free | 400 | 66 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 37h ago | free | 400 | 3222 ms | — | no | — | — | unexpected_status:400status_not_402 |