Leaderboard / cryptyx.ai / endpoint
GET https://cryptyx.ai/api/signals/composite/breadth
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 11 probes in the last 7 days.
- Category
- Signal by llm, confidence 35%
- Latest quote
- $0.05 on Base to 0x0cD2…394f
- 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-19 02:13 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 33h 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 |
|---|---|---|---|---|---|
| 33h ago | Signal | 35% | llm | v1 | claude-haiku-5-5: The path suggests a crypto market breadth composite signal from a trading-signals API, but the listing has no name, description, or tags, so the classification is a low-confidence inference from the URL alone. |
| 33h ago | Other | 20% | rules | v1 | rule none matched "" in none |
| 2d ago | Signal | 90% | rules | v1 | rule signal matched "regime" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 354 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 10h ago | free | 402 | 278 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 16h ago | free | 402 | 151 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 23h ago | free | 402 | 135 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 29h ago | free | 402 | 141 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 36h ago | free | 402 | 267 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 42h ago | free | 402 | 272 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 2d ago | free | 402 | 285 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 2d ago | free | 402 | 120 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 3d ago | free | 402 | 142 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |
| 3d ago | free | 402 | 146 ms | v2 | yes | $0.05 | 0x0cD2…394f | — |