Leaderboard / enforcement.cfsoft.us / endpoint
GET https://enforcement.cfsoft.us/v1/report
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
- Compliance by llm, confidence 80%
- Latest quote
- $0.5 on Base to 0xCa28…d816
- 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
- 4h ago
- Next probe
- 2026-11-18 05:45 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.5 | 0xCa28…d816 | authorization | yes | 6h 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 |
|---|---|---|---|---|---|
| 27h ago | Compliance | 80% | llm | v1 | claude-haiku-5-5: The endpoint returns enforcement records from public legal sources (agencies, courts, case numbers) for an organization, used for due diligence. This fits regulatory and sanctions-style compliance checks best, though it is also public records data. |
| 30h ago | Compliance | 60% | rules | v1 | rule compliance matched "legal compliance" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 519 ms | v2 | yes | $0.5 | 0xCa28…d816 | — |
| 11h ago | free | 402 | 556 ms | v2 | yes | $0.5 | 0xCa28…d816 | — |
| 17h ago | free | 402 | 405 ms | v2 | yes | $0.5 | 0xCa28…d816 | — |
| 23h ago | free | 402 | 342 ms | v2 | yes | $0.5 | 0xCa28…d816 | — |
| 30h ago | free | 402 | 288 ms | v2 | yes | $0.5 | 0xCa28…d816 | — |
| 36h ago | free | 402 | 67 ms | v2 | yes | $0.5 | 0xCa28…d816 | — |
| 42h ago | free | 402 | 122 ms | v2 | yes | $0.5 | 0xCa28…d816 | — |
| 2d ago | free | 402 | 322 ms | v2 | yes | $0.5 | 0xCa28…d816 | — |