Leaderboard / api.onhub.ai / endpoint
POST https://api.onhub.ai/v1/code
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 9 probes in the last 7 days.
- Category
- Computation by llm, confidence 60%
- Latest quote
- $0.015 on Base to 0x5388…C457
- 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-18 12:40 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.015 | 0x5388…C457 | default | yes | 51m 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 |
|---|---|---|---|---|---|
| 22h ago | Computation | 60% | llm | v1 | claude-haiku-5-5: The endpoint writes and runs Python to compute or verify an answer and returns code, output and a final answer, which fits computation. It could also be read as general code execution or inference, but the stated purpose centres on computing answers, so compute_math is the closest fit. |
| 38h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 663 ms | v2 | yes | $0.015 | 0x5388…C457 | — |
| 12h ago | free | 402 | 286 ms | v2 | yes | $0.015 | 0x5388…C457 | — |
| 18h ago | free | 402 | 115 ms | v2 | yes | $0.015 | 0x5388…C457 | — |
| 25h ago | free | 402 | 710 ms | v2 | yes | $0.015 | 0x5388…C457 | — |
| 31h ago | free | 402 | 820 ms | v2 | yes | $0.015 | 0x5388…C457 | — |
| 37h ago | free | 402 | 645 ms | v2 | yes | $0.015 | 0x5388…C457 | — |
| 43h ago | free | 402 | 695 ms | v2 | yes | $0.015 | 0x5388…C457 | — |
| 2d ago | free | 402 | 562 ms | v2 | yes | $0.015 | 0x5388…C457 | — |
| 2d ago | free | 402 | 870 ms | v2 | yes | $0.015 | 0x5388…C457 | — |