Leaderboard / encoding.openverbs.com / endpoint
POST https://encoding.openverbs.com/v1/detect
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
- Data transform by llm, confidence 85%
- Latest quote
- $0.002 on Base to 0xb3f4…194A
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 2h ago
- Next probe
- 2026-11-18 00:01 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.002 | 0xb3f4…194A | 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 |
|---|---|---|---|---|---|
| 6h ago | Data transform | 85% | llm | v1 | claude-haiku-5-5: The endpoint takes a base64 byte buffer and returns a detected character set, which is a deterministic byte-level transform/utility over input data. It is not a crypto, web, or inference service. data_transform fits best among the listed categories, though it is not a JSON/CSV or hash tool specifically, so confidence is moderately high rather than certain. |
| 23h ago | Data transform | 60% | rules | v1 | rule data_transform matched "base64" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 32 ms | v2 | yes | $0.002 | 0xb3f4…194A | — |
| 9h ago | free | 402 | 33 ms | v2 | yes | $0.002 | 0xb3f4…194A | — |
| 15h ago | free | 402 | 144 ms | v2 | yes | $0.002 | 0xb3f4…194A | — |
| 21h ago | free | 402 | 68 ms | v2 | yes | $0.002 | 0xb3f4…194A | — |
| 27h ago | free | 402 | 24 ms | v2 | yes | $0.002 | 0xb3f4…194A | — |
| 34h ago | free | 402 | 111 ms | v2 | yes | $0.002 | 0xb3f4…194A | — |
| 40h ago | free | 402 | 291 ms | v2 | yes | $0.002 | 0xb3f4…194A | — |