Paywary

Leaderboard / api.craigmbrown.com / endpoint

POST https://api.craigmbrown.com/v1/services/trust.receipt-verify

Scores measure reliability and honesty, not output quality.

81Payconfidence: medium
  • Answered 7 of 8 probes in the last 7 days (88%).
  • Answered 7 of 8 probes in the last 30 days (88%).
Category
Web audit by llm, confidence 35%
Latest quote
$0.01 on Base to 0x5E70…4EB9
Uptime
88% / 7d, 88% / 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 12:00 UTC

Score components

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

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.010x5E70…4EB9defaultyes39m ago
cdpexactPolygon0x3c49…3359100000x5E70…4EB9defaultyes39m 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
35h agoWeb audit35%llmv1claude-haiku-5-5: The endpoint verifies a BlindOracle receipt by checking proof rail membership, payload hashing and HMAC signatures. This is closest to a trust/verification service, but no listed category fits cleanly. web_audit is a weak fit since it audits a URL the caller supplies, and this checks receipts instead. dns_domain and compliance also fit poorly. Confidence is low, so 'other' may be more accurate.
38h agoData transform60%rulesv1rule data_transform matched "hash" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
6h agofree402103 msv2yes$0.010x5E70…4EB9—
18h agofreetimeout15013 ms————no_responsefetch_error:timeout
25h agofree402219 msv2yes$0.010x5E70…4EB9—
31h agofree4021740 msv2yes$0.010x5E70…4EB9—
37h agofree402104 msv2yes$0.010x5E70…4EB9—
43h agofree402148 msv2yes$0.010x5E70…4EB9—
2d agofree402469 msv2yes$0.010x5E70…4EB9—
2d agofree402109 msv2yes$0.010x5E70…4EB9—