Paywary

Leaderboard / quartermaster.surewhynot.app / endpoint

GET https://quartermaster.surewhynot.app/v1/tx-decode

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 9 probes in the last 7 days.
Category
Chain read by llm, confidence 80%
Latest quote
$0.003 on Base to 0x5253…19cb
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-18 12:19 UTC

Score components

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

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0030x5253…19cbdefaultyes4h ago
cdpexactSolanaEPjFWd…Dt1v3000FgcKNz…zXfadefaultyes4h ago

Listing changes

WhenEventFromTo
19h agoreappearedfalsetrue
19h agoreappearedfalsetrue
25h agodisappeared——
25h agodisappeared——

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
18h agoChain read80%llmv1claude-haiku-5-5: The endpoint decodes calldata of a Base transaction given its hash, which is a public chain data lookup returning a human-readable function call. It is a transaction/contract-level read, best matched by chain_read rather than data_transform, since it requires fetching on-chain transaction data by hash and interpreting ABI-encoded calls.
18h agox402 tooling60%rulesv1rule x402_meta matched "eip-3009" in description
25h agoOther15%llmv1claude-haiku-5-5: The listing has no description, tags, service name, or example fields. The path tx-decode suggests decoding a blockchain transaction, which would point to chain_read, but the listing alone does not confirm what the endpoint returns, so confidence is low.
25h agoOther20%rulesv1rule none matched "" in none
35h agox402 tooling60%rulesv1rule x402_meta matched "eip-3009" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
2h agofree4021119 msv2yes$0.0030x5253…19cb—
8h agofree40246 msv2yes$0.0030x5253…19cb—
15h agofree402535 msv2yes$0.0030x5253…19cb—
21h agofree402778 msv2yes$0.0030x5253…19cb—
27h agofree402514 msv2yes$0.0030x5253…19cb—
34h agofree402362 msv2yes$0.0030x5253…19cb—
40h agofree40275 msv2yes$0.0030x5253…19cb—
46h agofree40216 msv2yes$0.0030x5253…19cb—
2d agofree402760 msv2yes$0.0030x5253…19cb—