Leaderboard / relay.imagiolabs.com / endpoint
GET https://relay.imagiolabs.com/demand-graph
Scores measure reliability and honesty, not output quality.
- Listed only 3 days ago; new listings earn trust over 30 days.
- Answered all 12 probes in the last 7 days.
- Category
- Signal by llm, confidence 40%
- Latest quote
- $0.01 on Base to 0xcdd0…fb9d
- 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-19 10:54 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0xcdd0…fb9d | default | yes | 6h ago |
| payai | exact | Base | 0x8335…2913 | $0.01 | 0xcdd0…fb9d | default | yes | 6h ago |
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 47h ago | reappeared | false | true |
| 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 |
|---|---|---|---|---|---|
| 31h ago | Signal | 40% | llm | v1 | claude-haiku-5-5: Description suggests analytical market-demand report with scenario modeling, but tags conflict and the output is unclear. |
| 2d ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 1h ago | free | 402 | 20 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 7h ago | free | 402 | 511 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 13h ago | free | 402 | 1886 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 20h ago | free | 402 | 27 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 26h ago | free | 402 | 33 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 32h ago | free | 402 | 610 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 38h ago | free | 402 | 177 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 45h ago | free | 402 | 179 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 2d ago | free | 402 | 118 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 2d ago | free | 402 | 27 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 3d ago | free | 402 | 15 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |
| 3d ago | free | 402 | 178 ms | v2 | yes | $0.01 | 0xcdd0…fb9d | — |