Leaderboard / sicher.halowerk.com / endpoint
POST https://sicher.halowerk.com/v1/container-inspect
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
- DNS and domains by llm, confidence 35%
- Latest quote
- $0.005 on Base to 0x2880…4E5E
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 6h ago
- Next probe
- 2026-11-17 21:40 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.005 | 0x2880…4E5E | eip3009 | 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. 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 |
|---|---|---|---|---|---|
| 1h ago | DNS and domains | 35% | llm | v1 | claude-haiku-5-5: Returns registry manifest and image config metadata (digest, platforms, layers, entrypoint, ports). It is not a chain read, scrape, or web audit; closest fit is dns_domain for infrastructure lookup, but no perfect category exists, so confidence is moderate-low. Alternatively it could be data_transform, but registry inspection is infrastructure metadata rather than a deterministic transform. |
| 24h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 565 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 12h ago | free | 402 | 559 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 19h ago | free | 402 | 573 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 26h ago | free | 402 | 517 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 32h ago | free | 402 | 505 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 38h ago | free | 402 | 152 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |