Leaderboard / rubric-protocol.com / endpoint
POST https://rubric-protocol.com/v1/c2pa/verdict-attest/claim
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 8 probes in the last 7 days.
- Category
- Other by llm, confidence 20%
- Latest quote
- $0.05 on Base to 0xaB67…54ca
- 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 05:55 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 7h ago | disappeared | — | — |
| 7h ago | disappeared | — | — |
| 7h 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 |
|---|---|---|---|---|---|
| 7h ago | Other | 20% | llm | v1 | claude-haiku-5-5: The listing has no service name, tags, description, or example fields. The path suggests C2PA content credential verification and attestation, which could fit compliance or signal, but the listing gives too little to classify it confidently. |
| 7h ago | Commerce | 50% | rules | v1 | rule commerce matched "/claim" in metadata |
| 26h ago | Compliance | 60% | llm | v1 | claude-haiku-5-5: The endpoint countersigns and anchors attestations of C2PA content-provenance verdicts, which is closest to a compliance/verification service. It is not a signal or inference output, since it attests that an assertion was made rather than judging its truth. Tags include compliance, supporting this choice, though the provenance and attestation focus leaves some ambiguity. |
| 29h ago | Data transform | 60% | rules | v1 | rule data_transform matched "hash" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 250 ms | v2 | option ok | $0.05 | 0xaB67…54ca | malformed_challenge accepts[2].network_not_caip2 |
| 9h ago | free | 402 | 280 ms | v2 | option ok | $0.05 | 0xaB67…54ca | malformed_challenge accepts[2].network_not_caip2 |
| 16h ago | free | 402 | 86 ms | v2 | option ok | $0.05 | 0xaB67…54ca | malformed_challenge accepts[2].network_not_caip2 |
| 22h ago | free | 402 | 268 ms | v2 | option ok | $0.05 | 0xaB67…54ca | malformed_challenge accepts[2].network_not_caip2 |
| 28h ago | free | 402 | 230 ms | v2 | option ok | $0.05 | 0xaB67…54ca | malformed_challenge accepts[2].network_not_caip2 |
| 35h ago | free | 402 | 86 ms | v2 | option ok | $0.05 | 0xaB67…54ca | malformed_challenge accepts[2].network_not_caip2 |
| 41h ago | free | 402 | 90 ms | v2 | option ok | $0.05 | 0xaB67…54ca | malformed_challenge accepts[2].network_not_caip2 |
| 47h ago | free | 402 | 90 ms | v2 | option ok | $0.05 | 0xaB67…54ca | malformed_challenge accepts[2].network_not_caip2 |