Leaderboard / turboshop.ai / endpoint
POST https://turboshop.ai/api/v1/products/prod-ephemeral-key-vault-enterprise/buy
Scores measure reliability and honesty, not output quality.
- Quoted a price different from the listed price on 4 of 4 comparable probes.
- 3 probes got a response that was not a 402 payment challenge.
- Category
- Other by llm, confidence 20%
- Latest quote
- $0.02 on Base to 0x811C…2eBe
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 3h ago
- Next probe
- 2026-11-17 23:41 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 1h 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 |
|---|---|---|---|---|---|
| 1h ago | Other | 20% | llm | v1 | claude-haiku-5-5: The endpoint path suggests a commerce purchase of a product on a shop host, which points to commerce, but the listing has no service name, tags, or description, so the signal is weak and the category is only a guess from the URL path. |
| 1h ago | Other | 20% | rules | v1 | rule none matched "" in none |
| 7h ago | Commerce | 55% | llm | v1 | claude-haiku-5-5: The resource is a product buy endpoint on a shop host (/products/.../buy), so the caller is purchasing a product. Its description reads like key management and signing, which would otherwise suggest utility or other, but the URL and buy action point to commerce as the most specific fit. |
| 23h ago | Data transform | 60% | rules | v1 | rule data_transform matched "sha256" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 355 ms | v2 | yes | $0.02 | 0x811C…2eBe | price_below_listingprice_mismatchpayto_mismatch |
| 10h ago | free | 402 | 675 ms | v2 | yes | $0.02 | 0x811C…2eBe | price_below_listingprice_mismatchpayto_mismatch |
| 16h ago | free | 200 | 579 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 22h ago | free | 200 | 180 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 28h ago | free | 402 | 322 ms | v2 | yes | $0.02 | 0x811C…2eBe | price_below_listingprice_mismatchpayto_mismatch |
| 34h ago | free | 402 | 650 ms | v2 | yes | $0.02 | 0x811C…2eBe | price_below_listingprice_mismatchpayto_mismatch |
| 40h ago | free | 200 | 727 ms | — | no | — | — | no_payment_requiredstatus_not_402 |