Leaderboard / aipaygen.com / endpoint
GET https://aipaygen.com/data/security/uptime
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
- Other by llm, confidence 20%
- Latest quote
- $0.001 on Base to 0xebA2…35B0
- 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
- 2h ago
- Next probe
- 2026-11-18 10:21 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 16h 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 |
|---|---|---|---|---|---|
| 10h ago | Other | 20% | llm | v1 | claude-haiku-5-5: The listing has no service name, description, tags or example fields. The path hints at a security or uptime check, which could fall under web_audit or dns_domain, but the listing says too little to classify it confidently. |
| 16h ago | Other | 20% | rules | v1 | rule none matched "" in none |
| 33h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 854 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 8h ago | free | 402 | 2717 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 15h ago | free | 402 | 55 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 21h ago | free | 402 | 16 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 28h ago | free | 402 | 33 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 35h ago | free | 402 | 173 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 41h ago | free | 402 | 24 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 47h ago | free | 402 | 12 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |