Leaderboard / apiacre.com / endpoint
POST https://apiacre.com/v1/data/schema-validate
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
- Data transform by llm, confidence 35%
- Latest quote
- $0.01 on Base to 0xa0BF…869B
- 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
- 5h ago
- Next probe
- 2026-11-19 02:23 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 7h ago | disappeared | — | — |
| 7h 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 |
|---|---|---|---|---|---|
| 7h ago | Data transform | 35% | llm | v1 | claude-haiku-5-5: Path suggests schema validation of data, a deterministic transform, but no description or tags are provided to confirm. |
| 7h ago | Data transform | 50% | rules | v1 | rule data_transform matched "schema validate" in metadata |
| 41h ago | Data transform | 90% | llm | v1 | claude-haiku-5-5: The endpoint validates a JSON instance against a JSON Schema and returns deterministic pointers and error lists, which is a deterministic JSON tool, so data_transform fits best. |
| 2d ago | Data transform | 60% | rules | v1 | rule data_transform matched "json schema" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 597 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 12h ago | free | 402 | 571 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 18h ago | free | 402 | 589 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 25h ago | free | 402 | 606 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 31h ago | free | 402 | 237 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 38h ago | free | 402 | 752 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 44h ago | free | 402 | 214 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 2d ago | free | 402 | 536 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 2d ago | free | 402 | 636 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 3d ago | free | 402 | 203 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |
| 3d ago | free | 402 | 192 ms | v2 | yes | $0.01 | 0xa0BF…869B | — |