Paywary

Leaderboard / bruk-agent-api.fly.dev / endpoint

GET https://bruk-agent-api.fly.dev/v1/issuer-check

Scores measure reliability and honesty, not output quality.

92Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • 1 probe got a response that was not a 402 payment challenge.
Category
Chain read by llm, confidence 60%
Latest quote
$0.01 on Base to 0x6B1A…710b
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
4h ago
Next probe
2026-11-18 06:38 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
88w 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
cdpexactxrpl:0XRP7750r36sbD…oRQ4defaultyes6h ago
cdpexactxrpl:0524C55…0000—r36sbD…oRQ4defaultyes6h ago
cdpexactBase0x8335…2913$0.010x6B1A…710bdefaultyes6h 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
14h agoChain read60%llmv1claude-haiku-5-5: The endpoint inspects XRP Ledger account data (Domain field, issued tokens, control flags like freeze and clawback), which is on-chain state reading. It also verifies a domain's xrp-ledger.toml, which edges toward dns_domain or compliance, but the core output is chain account inspection.
31h agoData transform60%rulesv1rule data_transform matched "toml" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
4h agofree40289 msv2option ok$0.010x6B1A…710bmalformed_challenge
accepts[2].amount_not_uint_string
10h agofree402246 msv2option ok$0.010x6B1A…710bmalformed_challenge
accepts[2].amount_not_uint_string
17h agofree402211 msv2option ok$0.010x6B1A…710bmalformed_challenge
accepts[2].amount_not_uint_string
23h agofree402166 msv2option ok$0.010x6B1A…710bmalformed_challenge
accepts[2].amount_not_uint_string
29h agofree2002992 ms—no——no_payment_requiredstatus_not_402
35h agofree402651 msv2option ok$0.010x6B1A…710bmalformed_challenge
accepts[2].amount_not_uint_string
42h agofree40292 msv2option ok$0.010x6B1A…710bmalformed_challenge
accepts[2].amount_not_uint_string
2d agofree40286 msv2option ok$0.010x6B1A…710bmalformed_challenge
accepts[2].amount_not_uint_string