Leaderboard / api.firstmention.uk / endpoint
POST https://api.firstmention.uk/s/api-change-check/compare
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Web audit by llm, confidence 45%
- Latest quote
- $0.01 on Base to 0xddbe…E572
- 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-17 23:26 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0xddbe…E572 | default | yes | 1h 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 |
|---|---|---|---|---|---|
| 22h ago | Web audit | 45% | llm | v1 | claude-haiku-5-5: The endpoint diffs two OpenAPI specs supplied by the caller, reporting added or removed paths, methods, parameters and response codes. That is an audit of a supplied artifact rather than page content, a crypto or data feed, or a developer utility. None of the listed categories fits exactly; web_audit is the closest match since it covers audits of supplied inputs, but the spec-diff focus and the lack of a URL-based audit lower confidence. Other was considered but the description is specific enoug |
| 26h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 486 ms | v2 | yes | $0.01 | 0xddbe…E572 | — |
| 12h ago | free | 402 | 478 ms | v2 | yes | $0.01 | 0xddbe…E572 | — |
| 19h ago | free | 402 | 464 ms | v2 | yes | $0.01 | 0xddbe…E572 | — |
| 25h ago | free | 402 | 453 ms | v2 | yes | $0.01 | 0xddbe…E572 | — |
| 31h ago | free | 402 | 454 ms | v2 | yes | $0.01 | 0xddbe…E572 | — |
| 38h ago | free | 402 | 163 ms | v2 | yes | $0.01 | 0xddbe…E572 | — |
| 44h ago | free | 402 | 145 ms | v2 | yes | $0.01 | 0xddbe…E572 | — |