Leaderboard / api.syntalic.com / endpoint
GET https://api.syntalic.com/v1/shopper/price-history
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 9 probes in the last 7 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
- 6h ago
- Next probe
- 2026-11-18 16:04 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| payai | exact | Base | 0x8335…2913 | $0.01 | 0xe2e6…17fe | default | yes | 4h ago |
| 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 |
|---|---|---|---|---|---|
| 4h ago | Other | 30% | llm | v1 | claude-haiku-5-5: Description only says shopper pricing query with no service name or tags; price history for shopping items is unclear, so low confidence. |
| 4h ago | Crypto price | 50% | rules | v1 | rule crypto_price matched "/price" in metadata |
| 17h ago | Other | 30% | llm | v1 | claude-haiku-5-5: Shopper price-history endpoint could be retail price tracking, but the description is generic and the retailer fields are ambiguous. |
| 42h ago | Crypto price | 50% | rules | v1 | rule crypto_price matched "/price" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 156 ms | v2 | yes | $0.01 | 0xe2e6…17fe | — |
| 12h ago | free | 402 | 210 ms | v2 | yes | $0.01 | 0xe2e6…17fe | — |
| 18h ago | free | 402 | 214 ms | v2 | yes | $0.01 | 0xe2e6…17fe | — |
| 24h ago | free | 402 | 142 ms | v2 | yes | $0.01 | 0xe2e6…17fe | — |
| 30h ago | free | 402 | 106 ms | v2 | yes | $0.01 | 0xe2e6…17fe | — |
| 37h ago | free | 402 | 124 ms | v2 | yes | $0.01 | 0xe2e6…17fe | — |
| 44h ago | free | 402 | 216 ms | v2 | yes | $0.01 | 0xe2e6…17fe | — |
| 2d ago | free | 402 | 201 ms | v2 | yes | $0.01 | 0xe2e6…17fe | — |
| 2d ago | free | 402 | 99 ms | v2 | yes | $0.01 | 0xe2e6…17fe | — |