Paywary

Leaderboard / api.syntalic.com / endpoint

GET https://api.syntalic.com/v1/analyst/retailer-index

Scores measure reliability and honesty, not output quality.

80Payconfidence: medium
  • 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
Finance data by llm, confidence 35%
Latest quote
$0.02 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
2h ago
Next probe
2026-11-19 13:42 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
25w 15%
Price honesty
100w 15%
Delivery after payment
n/aexcluded
Wallet stability
100w 10%
Listing age
11w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
payaiexactBase0x8335…2913$0.020xe2e6…17fedefaultyes4h ago
payaiexactSolanaEPjFWd…Dt1v200002hYY7w…uB2Wdefaultyes4h 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.

WhenCategoryConfidenceMethodVersionEvidence
10h agoFinance data35%llmv1claude-haiku-5-5: Analyst market-level retailer index query; the description is vague, so it could be market or public data, with low confidence.
10h agoOther40%rulesv1rule none matched "" in none
16h agoOther30%llmv1claude-haiku-5-5: Description is generic 'analyst/market-level query' with no service name or tags; example fields suggest retailer market data but the content is unclear.
16h agoOther40%rulesv1rule none matched "" in none
29h agoOther30%llmv1claude-haiku-5-5: Description is vague: 'analyst/market-level query' with no stated data type, so the retailer index content cannot be determined confidently.
3d agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
2h agofree40282 msv2yes$0.020xe2e6…17fe—
9h agofree402115 msv2yes$0.020xe2e6…17fe—
15h agofree402267 msv2yes$0.020xe2e6…17fe—
22h agofree400152 ms—no——unexpected_status:400status_not_402
28h agofree400200 ms—no——unexpected_status:400status_not_402
35h agofree400209 ms—no——unexpected_status:400status_not_402
42h agofree400241 ms—no——unexpected_status:400status_not_402
2d agofree40079 ms—no——unexpected_status:400status_not_402
2d agofree400253 ms—no——unexpected_status:400status_not_402
3d agofree400357 ms—no——unexpected_status:400status_not_402
3d agofree400172 ms—no——unexpected_status:400status_not_402
3d agofree40071 ms—no——unexpected_status:400status_not_402