Leaderboard / api.extendivo.com / endpoint
POST https://api.extendivo.com/v1/safe-fetch-secure
Scores measure reliability and honesty, not output quality.
- The payment wallet changed in the last 7 days, which caps the verdict at caution until it has been stable for a week.
- The payment wallet changed 2 times in the last 30 days.
- Category
- Web scrape by llm, confidence 82%
- Latest quote
- $0.015 on Base to 0xc178…0edf
- Uptime
- 100% / 7d, 100% / 30d
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 23m ago
- Next probe
- 2026-11-17 10:42 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.015 | 0xc178…0edf | default | yes | 5h ago |
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 13h ago | payto_changed | 0xa62a446c7bfc1d3dea1465e1a52282c11ade98da | 0xc178bf873a3b484440c5cafc26fef1b6cd2a0edf |
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. Delivery results do not affect scores yet.
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 |
|---|---|---|---|---|---|
| 4h ago | Web scrape | 82% | llm | v1 | claude-haiku-5-5: The endpoint takes a URL and returns clean extracted text from the page for AI agents, which is a fetch-and-read of page content. The security features (SSRF protection, prompt-injection detection, risk scoring) are wrappers around that core function, so web_scrape fits best over web_audit, which audits a site's own properties. |
| 7h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 23m ago | free | 402 | 5106 ms | v2 | yes | $0.015 | 0xc178…0edf | — |
| 7h ago | free | 402 | 799 ms | v2 | yes | $0.015 | 0xc178…0edf | — |
| 13h ago | free | 402 | 1069 ms | v2 | yes | $0.015 | 0xc178…0edf | payto_changed |
| 19h ago | free | 402 | 739 ms | v2 | yes | $0.015 | 0xa62a…98da | — |
| 26h ago | free | 402 | 203 ms | v2 | yes | $0.015 | 0xa62a…98da | — |