Leaderboard / stack.halowerk.com / endpoint
POST https://stack.halowerk.com/stack/articles/complianz
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Web audit by llm, confidence 70%
- Latest quote
- $0.005 on Base to 0x2880…4E5E
- 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
- 4h ago
- Next probe
- 2026-11-18 00:09 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 | 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. 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 |
|---|---|---|---|---|---|
| 8h ago | Web audit | 70% | llm | v1 | claude-haiku-5-5: The endpoint takes a public URL the caller supplies and reports the site's detected technology stack, specifically whether the Complianz consent plugin is present, with evidence and optional version differences. That fits a site dependency or technology audit of a URL the caller provides. The description is technical and somewhat unclear, so confidence is moderate. |
| 25h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 183 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 11h ago | free | 402 | 496 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 17h ago | free | 402 | 160 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 23h ago | free | 402 | 452 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 29h ago | free | 402 | 157 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 35h ago | free | 402 | 152 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 41h ago | free | 402 | 152 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |