Paywary

Leaderboard / api.blockchainmoneymap.com / endpoint

POST https://api.blockchainmoneymap.com/api/x402/payment-preflight

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 10 probes in the last 7 days.
Category
Other by llm, confidence 15%
Latest quote
$0.01 on Base to 0x2211…713a
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
5h ago
Next probe
2026-11-18 19:00 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
9w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen

Listing changes

WhenEventFromTo
22h 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
22h agoOther15%llmv1claude-haiku-5-5: The endpoint path suggests a payment preflight check, which would fall under x402_meta, but there is no service name, tags, description, or example input to confirm what it returns. The path hints at x402 payment tooling, so x402_meta is plausible, but the listing alone is too thin to be confident, so I classify it as other with low confidence.
22h agoOther20%rulesv1rule none matched "" in none
27h agox402 tooling80%llmv1claude-haiku-5-5: The endpoint runs pre-payment checks for an agent before paying an x402 resource, validating payee, amount and resource URL. That is x402 payment tooling, so x402_meta fits best, though the mention of public-chain checks adds some ambiguity.
44h agox402 tooling60%rulesv1rule x402_meta matched "x402 resource" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
5h agofree402160 msv2yes$0.010x2211…713a—
11h agofree402148 msv2yes$0.010x2211…713a—
17h agofree402154 msv2yes$0.010x2211…713a—
24h agofree402286 msv2yes$0.010x2211…713a—
30h agofree402200 msv2yes$0.010x2211…713a—
36h agofree402170 msv2yes$0.010x2211…713a—
43h agofree402166 msv2yes$0.010x2211…713a—
2d agofree402224 msv2yes$0.010x2211…713a—
2d agofree402190 msv2yes$0.010x2211…713a—
3d agofree402159 msv2yes$0.010x2211…713a—