Leaderboard / api.syntalic.com / endpoint
GET https://api.syntalic.com/v1/reference/reverse
Scores measure reliability and honesty, not output quality.
- 9 probes got a response that was not a 402 payment challenge.
- Listed only 3 days ago; new listings earn trust over 30 days.
- Category
- Other by llm, confidence 30%
- Latest quote
- $0.01 on Base to 0xe2e6…17fe
- 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-19 12:35 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| payai | exact | Solana | EPjFWd…Dt1v | 10000 | 2hYY7w…uB2W | default | yes | 4h 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 |
|---|---|---|---|---|---|
| 16h ago | Other | 30% | llm | v1 | claude-haiku-5-5: Taxonomy reference lookup by gpc_code is vague; it may map product codes, but the listing lacks clear detail. |
| 16h ago | Other | 40% | rules | v1 | rule none matched "" in none |
| 35h ago | Other | 30% | llm | v1 | claude-haiku-5-5: Description is a generic taxonomy reference lookup with no service name, tags, or example fields to clarify what data is returned. |
| 3d ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 97 ms | v2 | yes | $0.01 | 0xe2e6…17fe | listed_option_not_quoted |
| 10h ago | free | 402 | 94 ms | v2 | yes | $0.01 | 0xe2e6…17fe | listed_option_not_quoted |
| 16h ago | free | 402 | 246 ms | v2 | yes | $0.01 | 0xe2e6…17fe | listed_option_not_quoted |
| 22h ago | free | 400 | 130 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 29h ago | free | 400 | 91 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 35h ago | free | 400 | 93 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 42h ago | free | 400 | 94 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 2d ago | free | 400 | 300 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 2d ago | free | 400 | 100 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 3d ago | free | 400 | 274 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 3d ago | free | 400 | 121 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 3d ago | free | 400 | 186 ms | — | no | — | — | unexpected_status:400status_not_402 |