Leaderboard / api.xynaptic.io / endpoint
GET https://api.xynaptic.io/v1/crypto-orderflow
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 10 probes in the last 7 days.
- Category
- Crypto price by llm, confidence 35%
- Latest quote
- $0.05 on Base to 0x4ff8…D5e9
- 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
- 14m 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 |
|---|---|---|---|
| 2d ago | disappeared | — | — |
| 2d ago | disappeared | — | — |
| 2d 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 |
|---|---|---|---|---|---|
| 30h ago | Crypto price | 35% | llm | v1 | claude-haiku-5-5: The resource name suggests crypto order flow data, which is closest to market snapshots for crypto assets, but there is no description, tags, or example fields to confirm what it returns, so confidence is low. |
| 47h ago | Other | 20% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 14m ago | free | 402 | 1468 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 8h ago | free | 402 | 8 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 14h ago | free | 402 | 28 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 20h ago | free | 402 | 91 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 27h ago | free | 402 | 30 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 33h ago | free | 402 | 55 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 39h ago | free | 402 | 62 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 45h ago | free | 402 | 29 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 2d ago | free | 402 | 50 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 2d ago | free | 402 | 27 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |
| 3d ago | free | 402 | 13 ms | v2 | yes | $0.05 | 0x4ff8…D5e9 | — |