Leaderboard / api.niftibot.com / endpoint
GET https://api.niftibot.com/v1/companies/:company_number
Scores measure reliability and honesty, not output quality.
- Responded without asking for payment on 11 probes; it may no longer be an x402 endpoint.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Category
- Enrichment by llm, confidence 55%
- Latest quote
- — on — to —
- 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
- 2h ago
- Next probe
- 2026-11-19 02:13 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base Sepolia | 0x036C…CF7e | 10000 | 0xA17d…94E1 | default | yes | 4h 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 |
|---|---|---|---|---|---|
| 32h ago | Enrichment | 55% | llm | v1 | claude-haiku-5-5: Returns a company profile looked up by company number, which matches company lookup under enrichment. The description also mentions a compliance verdict, which could point to compliance, but the core output is a company profile from Companies House data. |
| 2d ago | Enrichment | 60% | rules | v1 | rule enrichment matched "companies house" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 400 | 462 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 9h ago | free | 400 | 457 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 15h ago | free | 400 | 446 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 21h ago | free | 400 | 418 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 28h ago | free | 400 | 495 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 34h ago | free | 400 | 476 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 41h ago | free | 400 | 482 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 47h ago | free | 400 | 463 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 2d ago | free | 400 | 450 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 2d ago | free | 400 | 451 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 3d ago | free | 400 | 466 ms | — | no | — | — | unexpected_status:400status_not_402 |