Leaderboard / einvoice.alexhub.uk / endpoint
POST https://einvoice.alexhub.uk/v1/fix
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
- Data transform by llm, confidence 60%
- Latest quote
- $0.05 on Base to 0x53d9…84ce
- 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 12:05 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.05 | 0x53d9…84ce | default | yes | 54m 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 |
|---|---|---|---|---|---|
| 35h ago | Data transform | 60% | llm | v1 | claude-haiku-5-5: The endpoint takes an invoice XML and returns a corrected XML with a change list, which is a deterministic document repair rather than compliance screening or a filing. Compliance was considered, but the output is a transformed document, so data_transform fits better, with moderate confidence since it also validates against e-Factura rules. |
| 38h ago | Data transform | 60% | rules | v1 | rule data_transform matched "xml" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 722 ms | v2 | yes | $0.05 | 0x53d9…84ce | — |
| 12h ago | free | 402 | 614 ms | v2 | yes | $0.05 | 0x53d9…84ce | — |
| 19h ago | free | 402 | 682 ms | v2 | yes | $0.05 | 0x53d9…84ce | — |
| 25h ago | free | 402 | 596 ms | v2 | yes | $0.05 | 0x53d9…84ce | — |
| 31h ago | free | 402 | 583 ms | v2 | yes | $0.05 | 0x53d9…84ce | — |
| 37h ago | free | 402 | 606 ms | v2 | yes | $0.05 | 0x53d9…84ce | — |
| 44h ago | free | 402 | 679 ms | v2 | yes | $0.05 | 0x53d9…84ce | — |
| 2d ago | free | 402 | 620 ms | v2 | yes | $0.05 | 0x53d9…84ce | — |
| 2d ago | free | 402 | 213 ms | v2 | yes | $0.05 | 0x53d9…84ce | — |