Leaderboard / api.mekler.ai / endpoint
POST https://api.mekler.ai/v1/data/json/repair-or-convert-document
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 85%
- Latest quote
- $0.005 on Base to 0xF6c6…07c5
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 4h ago
- Next probe
- 2026-11-17 23:00 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.005 | 0xF6c6…07c5 | eip3009 | yes | 2h ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 5000 | 9mMDrH…USRc | default | yes | 2h 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 |
|---|---|---|---|---|---|
| 20h ago | Data transform | 85% | llm | v1 | claude-haiku-5-5: The endpoint repairs JSON syntax and converts between JSON and YAML, returning deterministic transformed text. This matches data_transform (JSON/CSV tools and deterministic transforms) rather than document conversion, since the input is structured data, not files like PDFs. |
| 23h ago | Data transform | 60% | rules | v1 | rule data_transform matched "yaml" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 459 ms | v2 | yes | $0.005 | 0xF6c6…07c5 | — |
| 11h ago | free | 402 | 453 ms | v2 | yes | $0.005 | 0xF6c6…07c5 | — |
| 17h ago | free | 402 | 539 ms | v2 | yes | $0.005 | 0xF6c6…07c5 | — |
| 23h ago | free | 402 | 486 ms | v2 | yes | $0.005 | 0xF6c6…07c5 | — |
| 29h ago | free | 402 | 421 ms | v2 | yes | $0.005 | 0xF6c6…07c5 | — |
| 35h ago | free | 402 | 291 ms | v2 | yes | $0.005 | 0xF6c6…07c5 | — |
| 42h ago | free | 402 | 370 ms | v2 | yes | $0.005 | 0xF6c6…07c5 | — |