Paywary

Leaderboard / audit.liquidlogicx.com / endpoint

GET https://audit.liquidlogicx.com/api/audit

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 1 day ago; new listings earn trust over 30 days.
  • Answered all 7 probes in the last 7 days.
Category
Web audit by llm, confidence 50%
Latest quote
$0.03 on Base to 0x1479…8c7b
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
18m ago
Next probe
2026-11-18 05:51 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
6w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.030x1479…8c7bdefaultyes2h 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
23h agoWeb audit50%llmv1claude-haiku-5-5: The endpoint audits an x402 agent wallet's public payment history on Base, returning payment counts, USDC totals and per-endpoint breakdowns. It is an audit of a wallet rather than a URL, so web_audit is a partial fit; chain_read is also plausible since it reads public-ledger data, but the output is an analytical audit report rather than raw chain data.
26h agoChain read60%rulesv1rule chain_read matched "in:wallet" in metadata

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
18m agofree402436 msv2yes$0.030x1479…8c7b—
7h agofree402499 msv2yes$0.030x1479…8c7b—
14h agofree402561 msv2yes$0.030x1479…8c7b—
20h agofree402384 msv2yes$0.030x1479…8c7b—
26h agofree402652 msv2yes$0.030x1479…8c7b—
32h agofree402521 msv2yes$0.030x1479…8c7b—
38h agofree402648 msv2yes$0.030x1479…8c7b—
45h agofree402350 msv2yes$0.030x1479…8c7b—