Leaderboard / http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run / endpoint
POST https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/release/changed
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 scrape by llm, confidence 40%
- Latest quote
- $0.002 on Base to 0xb48D…f7a9
- 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:53 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 | 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 |
|---|---|---|---|---|---|
| 16h ago | Web scrape | 40% | llm | v1 | claude-haiku-5-5: The endpoint checks whether a public GitHub release changed by fingerprinting its metadata and comparing hashes; it is a release change-detection tool, not a clear fit for any listed category. Closest is web_scrape since it fetches release metadata from GitHub, but confidence is modest because it returns a hash comparison rather than page content. |
| 26h ago | Data transform | 60% | rules | v1 | rule data_transform matched "sha-256" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 155 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 12h ago | free | 402 | 527 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 19h ago | free | 402 | 503 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 25h ago | free | 402 | 451 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 31h ago | free | 402 | 156 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 37h ago | free | 402 | 147 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |
| 43h ago | free | 402 | 153 ms | v2 | yes | $0.002 | 0xb48D…f7a9 | — |