Leaderboard / scraper-production-6a87.up.railway.app / endpoint
POST https://scraper-production-6a87.up.railway.app/v1/extract
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 80%
- Latest quote
- $0.02 on Base to 0x0395…637c
- 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
- 5h ago
- Next probe
- 2026-11-17 23:48 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.02 | 0x0395…637c | default | yes | 27m 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 |
|---|---|---|---|---|---|
| 9h ago | Web scrape | 80% | llm | v1 | claude-haiku-5-5: The endpoint takes a URL and a JSON schema and returns structured JSON extracted from the page, which is page content retrieval (scraping) with schema-driven output. Tags also point to web scraping. It could arguably be data_transform or inference, but fetching and extracting from a supplied URL matches web_scrape best. |
| 25h ago | Data transform | 60% | rules | v1 | rule data_transform matched "json schema" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 393 ms | v2 | yes | $0.02 | 0x0395…637c | — |
| 12h ago | free | 402 | 628 ms | v2 | yes | $0.02 | 0x0395…637c | — |
| 18h ago | free | 402 | 206 ms | v2 | yes | $0.02 | 0x0395…637c | — |
| 24h ago | free | 402 | 471 ms | v2 | yes | $0.02 | 0x0395…637c | — |
| 30h ago | free | 402 | 303 ms | v2 | yes | $0.02 | 0x0395…637c | — |
| 36h ago | free | 402 | 239 ms | v2 | yes | $0.02 | 0x0395…637c | — |
| 42h ago | free | 402 | 195 ms | v2 | yes | $0.02 | 0x0395…637c | — |