Leaderboard / compute-api-production-245d.up.railway.app / endpoint
POST https://compute-api-production-245d.up.railway.app/validate-json
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
- Data transform by llm, confidence 70%
- Latest quote
- $0.001 on Base to 0xb509…d959
- 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-18 04:03 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.001 | 0xb509…d959 | default | yes | 3h ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 1000 | GKbRLT…G7iP | default | yes | 3h ago |
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 3h ago | reappeared | false | true |
| 3h ago | reappeared | false | true |
| 5h ago | disappeared | — | — |
| 5h 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 |
|---|---|---|---|---|---|
| 3h ago | Data transform | 70% | llm | v1 | claude-haiku-5-5: Validating JSON input is a deterministic JSON tool, though the description is very brief and lacks detail. |
| 3h ago | Data transform | 50% | rules | v1 | rule data_transform matched "json validate" in metadata |
| 5h ago | Data transform | 35% | llm | v1 | claude-haiku-5-5: The path /validate-json suggests a deterministic JSON validation tool, which maps to data_transform. The listing has no description, service name, or tags, so confidence is low. |
| 5h ago | Data transform | 50% | rules | v1 | rule data_transform matched "json validate" in metadata |
| 27h ago | Data transform | 50% | rules | v1 | rule data_transform matched "json validate" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 89 ms | v2 | yes | $0.001 | 0xb509…d959 | — |
| 9h ago | free | 402 | 77 ms | v2 | yes | $0.001 | 0xb509…d959 | — |
| 16h ago | free | 402 | 18 ms | v2 | yes | $0.001 | 0xb509…d959 | — |
| 23h ago | free | 402 | 10 ms | v2 | yes | $0.001 | 0xb509…d959 | — |
| 30h ago | free | 402 | 77 ms | v2 | yes | $0.001 | 0xb509…d959 | — |
| 36h ago | free | 402 | 79 ms | v2 | yes | $0.001 | 0xb509…d959 | — |
| 42h ago | free | 402 | 14 ms | v2 | yes | $0.001 | 0xb509…d959 | — |