Paywary

Leaderboard / commandguard.grindfree.net / endpoint

POST https://commandguard.grindfree.net/v1/sql

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 9 probes in the last 7 days.
Category
Signal by llm, confidence 50%
Latest quote
$0.001 on Base to 0xe4b5…721b
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 12:15 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
8w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0010xe4b5…721bdefaultyes5h 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
32h agoSignal50%llmv1claude-haiku-5-5: CommandGuard returns an allow/warn/block verdict with rule codes on agent-generated SQL, which is a risk verdict. It is not a data lookup or transform, so signal fits best, though the security-guardrail purpose is not a perfect match for any listed category.
36h agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
3h agofree402250 msv2yes$0.0010xe4b5…721b—
10h agofree402347 msv2yes$0.0010xe4b5…721b—
16h agofree402507 msv2yes$0.0010xe4b5…721b—
23h agofree402272 msv2yes$0.0010xe4b5…721b—
29h agofree402391 msv2yes$0.0010xe4b5…721b—
35h agofree402419 msv2yes$0.0010xe4b5…721b—
41h agofree4021143 msv2yes$0.0010xe4b5…721b—
2d agofree402297 msv2yes$0.0010xe4b5…721b—
2d agofree402319 msv2yes$0.0010xe4b5…721b—