Leaderboard / hcrb.in / endpoint
POST https://hcrb.in/multimodal/verify-artifact
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 11 probes in the last 7 days.
- Category
- Compliance by llm, confidence 50%
- Latest quote
- $0.01 on Base to 0xc59c…6235
- 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
- 4m ago
- Next probe
- 2026-11-19 08:43 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0xc59c…6235 | default | yes | 3h ago |
| cdp | exact | Polygon | 0x3c49…3359 | 10000 | 0xc59c…6235 | default | yes | 3h ago |
| cdp | exact | Base | 0x60a3…db42 | $0.01 | 0xc59c…6235 | default | yes | 3h 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 |
|---|---|---|---|---|---|
| 31h ago | Compliance | 50% | llm | v1 | claude-haiku-5-5: The description mentions invoice/XML/UBL attestation across registries and currencies, with example fields like IBAN, organisation number and counterparty name, which suggests invoice verification and counterparty checks for compliance. The purpose is not fully clear from the listing, so confidence is moderate. |
| 2d 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 |
|---|---|---|---|---|---|---|---|---|
| 4m ago | free | 402 | 537 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 6h ago | free | 402 | 709 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 14h ago | free | 402 | 522 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 20h ago | free | 402 | 1130 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 26h ago | free | 402 | 1042 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 33h ago | free | 402 | 545 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 39h ago | free | 402 | 734 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 45h ago | free | 402 | 760 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 2d ago | free | 402 | 734 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 2d ago | free | 402 | 990 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 3d ago | free | 402 | 634 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |
| 3d ago | free | 402 | 669 ms | v2 | yes | $0.01 | 0xc59c…6235 | — |