Paywary

Leaderboard / rubric-protocol.com / endpoint

POST https://rubric-protocol.com/v1/x402/statement

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 1 day ago; new listings earn trust over 30 days.
  • Answered all 8 probes in the last 7 days.
Category
x402 tooling by llm, confidence 60%
Latest quote
$0.5 on Base to 0xaB67…54ca
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
3h ago
Next probe
2026-11-18 05:22 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.50xaB67…54cadefaultyes4h 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
26h agox402 tooling60%llmv1claude-haiku-5-5: The endpoint returns a signed monthly statement of x402 payment spend for an agent, with per-payment lines and a Merkle root, which is payment-tooling output rather than any listed domain. The billing and audit tags suggest a payments ledger, but 'commerce' fits a prepaid or listing service less well than x402_meta fits an x402 payment-header or spend tool. Confidence is moderate because the description is clear about the payment focus but the category set has no exact match for a billing attest
29h agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
3h agofree40286 msv2yes$0.50xaB67…54ca—
10h agofree40292 msv2yes$0.50xaB67…54ca—
16h agofree402104 msv2yes$0.50xaB67…54ca—
23h agofree402259 msv2yes$0.50xaB67…54ca—
29h agofree402260 msv2yes$0.50xaB67…54ca—
35h agofree40283 msv2yes$0.50xaB67…54ca—
41h agofree40281 msv2yes$0.50xaB67…54ca—
47h agofree40286 msv2yes$0.50xaB67…54ca—