Leaderboard / karte.halowerk.com / endpoint
POST https://karte.halowerk.com/v1/trip-metrics
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.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
- 2h ago
- Next probe
- 2026-11-18 16:10 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 | 54m ago |
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 29h ago | reappeared | false | true |
| 35h ago | disappeared | — | — |
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 |
|---|---|---|---|---|---|
| 16h ago | Computation | 60% | llm | v1 | claude-haiku-5-5: The endpoint takes GPS trace points with timestamps and returns computed distance, moving/stop time, speeds and energy consumption, which is a deterministic computation over supplied data. It is not a chain read, public dataset, or web resource, so compute_math fits best, though it is vehicle telemetry analytics and not a stated scientific formula. |
| 29h ago | Public data | 60% | rules | v1 | rule public_data matched "vehicle" in description |
| 35h ago | Other | 20% | rules | v1 | rule none matched "" in none |
| 38h ago | Public data | 60% | rules | v1 | rule public_data matched "vehicle" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 472 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 8h ago | free | 402 | 461 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 14h ago | free | 402 | 540 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 21h ago | free | 402 | 187 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 27h ago | free | 402 | 162 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 34h ago | free | 402 | 163 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 41h ago | free | 402 | 481 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 47h ago | free | 402 | 460 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |
| 2d ago | free | 402 | 151 ms | v2 | yes | $0.005 | 0x2880…4E5E | — |