Leaderboard / serp402.com / endpoint
POST https://serp402.com/api/v1/google-sports
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 search by llm, confidence 80%
- Latest quote
- $0.05 on Base to 0xAA12…C56d
- 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:42 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.05 | 0xAA12…C56d | default | yes | 48m ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 50000 | 6srFz6…CvbK | default | yes | 48m 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 |
|---|---|---|---|---|---|
| 16h ago | Web search | 80% | llm | v1 | claude-haiku-5-5: Google Sports results are a search-engine style output (Google SERP-derived sports results) returned as JSON, so web_search fits best, though the sports focus could suggest public_data. |
| 26h ago | Public data | 60% | rules | v1 | rule public_data matched "sports results" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 105 ms | v2 | yes | $0.05 | 0xAA12…C56d | — |
| 12h ago | free | 402 | 171 ms | v2 | yes | $0.05 | 0xAA12…C56d | — |
| 18h ago | free | 402 | 99 ms | v2 | yes | $0.05 | 0xAA12…C56d | — |
| 24h ago | free | 402 | 99 ms | v2 | yes | $0.05 | 0xAA12…C56d | — |
| 31h ago | free | 402 | 94 ms | v2 | yes | $0.05 | 0xAA12…C56d | — |
| 37h ago | free | 402 | 114 ms | v2 | yes | $0.05 | 0xAA12…C56d | — |
| 43h ago | free | 402 | 101 ms | v2 | yes | $0.05 | 0xAA12…C56d | — |