Leaderboard / relayzero.ai / endpoint
POST https://relayzero.ai/v1/intel/scan/batch
Scores measure reliability and honesty, not output quality.
- Responded without asking for payment on 10 probes; it may no longer be an x402 endpoint.
- 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
- 46m ago
- Next probe
- 2026-11-18 23:50 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| payai | exact | Solana | EPjFWd…Dt1v | 100000 | 2CkpGo…zL4H | default | yes | 58m 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 |
|---|---|---|---|---|---|
| 14h ago | Other | 20% | llm | v1 | claude-haiku-5-5: The listing has no name, tags, description or examples; the path 'intel/scan/batch' hints at scanning but is too vague to classify. |
| 45h ago | Other | 20% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 46m ago | free | 410 | 213 ms | — | no | — | — | not_foundstatus_not_402 |
| 7h ago | free | 410 | 226 ms | — | no | — | — | not_foundstatus_not_402 |
| 13h ago | free | 410 | 207 ms | — | no | — | — | not_foundstatus_not_402 |
| 20h ago | free | 410 | 222 ms | — | no | — | — | not_foundstatus_not_402 |
| 26h ago | free | 410 | 241 ms | — | no | — | — | not_foundstatus_not_402 |
| 33h ago | free | 410 | 229 ms | — | no | — | — | not_foundstatus_not_402 |
| 40h ago | free | 410 | 243 ms | — | no | — | — | not_foundstatus_not_402 |
| 46h ago | free | 410 | 214 ms | — | no | — | — | not_foundstatus_not_402 |
| 2d ago | free | 410 | 233 ms | — | no | — | — | not_foundstatus_not_402 |
| 2d ago | free | 410 | 219 ms | — | no | — | — | not_foundstatus_not_402 |