Leaderboard / http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run / endpoint
POST https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/http/latency
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 60%
- Latest quote
- $0.002 on Base to 0xb48D…f7a9
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 5h ago
- Next probe
- 2026-11-17 23:10 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.002 | 0xb48D…f7a9 | default | yes | 2h 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 |
|---|---|---|---|---|---|
| 14h ago | Web audit | 60% | llm | v1 | claude-haiku-5-5: The endpoint measures HTTP latency of a caller-supplied public URL, which resembles a site performance audit of a URL the caller provides. It is not a chain read, DNS lookup, or scrape, so web_audit is the closest fit, with moderate confidence since it could also be read as dns_domain network diagnostics. |
| 24h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 159 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 11h ago | free | 402 | 468 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 17h ago | free | 402 | 492 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 23h ago | free | 402 | 460 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 29h ago | free | 402 | 148 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 36h ago | free | 402 | 153 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 42h ago | free | 402 | 152 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |