Leaderboard / aipaygen.com / endpoint
GET https://aipaygen.com/data/holidays
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Other by llm, confidence 30%
- 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
- 1h ago
- Next probe
- 2026-11-18 04:14 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.001 | 0xebA2…35B0 | default | yes | 1h 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 |
|---|---|---|---|---|---|
| 3h ago | Other | 30% | llm | v1 | claude-haiku-5-5: The listing gives only the generic description 'Data utility endpoint' with a resource path suggesting holiday data, but no service name, tags, or example fields. The path hints at public calendar data, which would fit public_data, yet 'data utility' is too vague to classify confidently, so 'other' with low confidence is the honest choice. |
| 26h ago | Utility | 60% | rules | v1 | rule utility matched "holidays" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 1h ago | free | 402 | 103 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 8h ago | free | 402 | 48 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 15h ago | free | 402 | 23 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 21h ago | free | 402 | 24 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 28h ago | free | 402 | 102 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 34h ago | free | 402 | 136 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |
| 41h ago | free | 402 | 11 ms | v2 | yes | $0.001 | 0xebA2…35B0 | — |