Leaderboard / wallet.halowerk.com / endpoint
POST https://wallet.halowerk.com/v1/permit2-scope-auditor
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 35%
- Latest quote
- $0.001 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
- 6h ago
- Next probe
- 2026-11-18 00:08 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.001 | 0x2880…4E5E | eip3009 | 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. 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 |
|---|---|---|---|---|---|
| 10h ago | Web audit | 35% | llm | v1 | claude-haiku-5-5: The endpoint audits Permit/Permit2 approval scope from caller-supplied evidence rather than querying a chain, so it does not fit chain_read. It is not a URL audit either, and no tags or service name are given. The closest bucket is compliance-style risk verdicts, but the listing says nothing explicit about the output type, so confidence is low. |
| 26h 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 | 230 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 12h ago | free | 402 | 254 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 18h ago | free | 402 | 721 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 25h ago | free | 402 | 219 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 31h ago | free | 402 | 711 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 37h ago | free | 402 | 687 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 43h ago | free | 402 | 201 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |