Leaderboard / api.wsystem.dev / endpoint
POST https://api.wsystem.dev/company/batch
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 8 probes in the last 7 days.
- Category
- Enrichment by llm, confidence 80%
- Latest quote
- $0.1 on Base to 0xfbbe…714c
- 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
- 3h ago
- Next probe
- 2026-11-18 06:12 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.1 | 0xfbbe…714c | default | yes | 5h 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 |
|---|---|---|---|---|---|
| 20h ago | Enrichment | 80% | llm | v1 | claude-haiku-5-5: Batch company registry lookup in official business registers returns company records for up to 25 queries, which matches company lookup under enrichment. Tags such as kyb and sanctions suggest compliance use, but the endpoint itself returns company data rather than a compliance verdict. |
| 29h ago | Enrichment | 60% | rules | v1 | rule enrichment matched "company registry" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 510 ms | v2 | yes | $0.1 | 0xfbbe…714c | — |
| 9h ago | free | 402 | 206 ms | v2 | yes | $0.1 | 0xfbbe…714c | — |
| 16h ago | free | 402 | 205 ms | v2 | yes | $0.1 | 0xfbbe…714c | — |
| 22h ago | free | 402 | 229 ms | v2 | yes | $0.1 | 0xfbbe…714c | — |
| 28h ago | free | 402 | 485 ms | v2 | yes | $0.1 | 0xfbbe…714c | — |
| 35h ago | free | 402 | 201 ms | v2 | yes | $0.1 | 0xfbbe…714c | — |
| 41h ago | free | 402 | 176 ms | v2 | yes | $0.1 | 0xfbbe…714c | — |
| 47h ago | free | 402 | 178 ms | v2 | yes | $0.1 | 0xfbbe…714c | — |