Leaderboard / getskavio.com / endpoint
POST https://getskavio.com/x402/v1/web/extract/analyze
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 8 probes in the last 7 days.
- Category
- Web scrape by llm, confidence 60%
- Latest quote
- $0.03 on Base to 0x62BB…C139
- 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-18 05:38 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.03 | 0x62BB…C139 | default | yes | 6h 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 |
|---|---|---|---|---|---|
| 27h ago | Web scrape | 60% | llm | v1 | claude-haiku-5-5: The endpoint fetches a URL supplied by the caller and extracts its content, then applies LLM analysis. The core output is page content analysis tied to a web fetch, which best fits web_scrape, though the DeepSeek analysis component suggests some overlap with inference. |
| 31h ago | Inference | 60% | rules | v1 | rule inference matched "deepseek" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 232 ms | v2 | yes | $0.03 | 0x62BB…C139 | — |
| 11h ago | free | 402 | 664 ms | v2 | yes | $0.03 | 0x62BB…C139 | — |
| 18h ago | free | 402 | 550 ms | v2 | yes | $0.03 | 0x62BB…C139 | — |
| 24h ago | free | 402 | 711 ms | v2 | yes | $0.03 | 0x62BB…C139 | — |
| 30h ago | free | 402 | 202 ms | v2 | yes | $0.03 | 0x62BB…C139 | — |
| 36h ago | free | 402 | 299 ms | v2 | yes | $0.03 | 0x62BB…C139 | — |
| 43h ago | free | 402 | 599 ms | v2 | yes | $0.03 | 0x62BB…C139 | — |
| 2d ago | free | 402 | 608 ms | v2 | yes | $0.03 | 0x62BB…C139 | — |