Leaderboard / evidence402.onrender.com / endpoint
POST https://evidence402.onrender.com/api/v1/site-profile
Scores measure reliability and honesty, not output quality.
- 5 probes got a response that was not a 402 payment challenge.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Category
- Other by llm, confidence 20%
- Latest quote
- — on — to —
- 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
- 3h ago
- Next probe
- 2026-11-18 18:25 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 32h ago | disappeared | — | — |
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 |
|---|---|---|---|---|---|
| 32h ago | Other | 20% | llm | v1 | claude-haiku-5-5: The endpoint name 'site-profile' hints at a web audit or site profiling of a supplied URL, but there is no service name, tags, or description to confirm what it returns, so the classification is low confidence. |
| 32h ago | Other | 20% | rules | v1 | rule none matched "" in none |
| 38h ago | Web scrape | 60% | llm | v1 | claude-haiku-5-5: The endpoint takes a URL and returns the site's published description, structured data, pricing, contact and social links, which is page content extraction. It could also be seen as a web_audit, but it reports source claims rather than auditing security, SEO or dependencies, so web_scrape fits best. |
| 42h ago | Web scrape | 60% | rules | v1 | rule web_scrape matched "extraction agent-tools evidence402 onrender com in:url" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 400 | 210 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 9h ago | free | 400 | 186 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 16h ago | free | 400 | 378 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 22h ago | free | 400 | 237 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 29h ago | free | 400 | 225 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 35h ago | free | 402 | 233 ms | v2 | yes | $0.01 | 0xc606…176D | — |
| 41h ago | free | 402 | 225 ms | v2 | yes | $0.01 | 0xc606…176D | — |
| 47h ago | free | 402 | 315 ms | v2 | yes | $0.01 | 0xc606…176D | — |
| 2d ago | free | 402 | 183 ms | v2 | yes | $0.01 | 0xc606…176D | — |
| 3d ago | free | 402 | 229 ms | v2 | yes | $0.01 | 0xc606…176D | — |