Paywary

Leaderboard / agent-exec.448c.org / endpoint

POST https://agent-exec.448c.org/claim

Scores measure reliability and honesty, not output quality.

85Payconfidence: medium
  • 3 probes got a response that was not a 402 payment challenge.
  • Listed only 2 days ago; new listings earn trust over 30 days.
Category
Utility by llm, confidence 35%
Latest quote
$0.01 on Base to 0xc8Fc…2Ff0
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
2m ago
Next probe
2026-11-18 16:23 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
63w 15%
Price honesty
90w 15%
Delivery after payment
n/aexcluded
Wallet stability
100w 10%
Listing age
8w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
payaiexactBase0x8335…2913$0.00520xc8Fc…2Ff0defaultyes6h 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 agoUtility35%llmv1claude-haiku-5-5: The endpoint is a coordination primitive: it atomically claims a named key with a TTL and reports the current holder. It returns no chain, price, search, or content data, so none of the specific categories fit cleanly. It is closest to a utility or lock service, but confidence is low because the listing is terse and the category set has no lock or coordination entry.
37h agoCommerce60%rulesv1rule commerce matched "/claim" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
2m agofree402537 msv2yes$0.010xc8Fc…2Ff0price_above_listingprice_mismatch
6h agofree402445 msv2yes$0.010xc8Fc…2Ff0price_above_listingprice_mismatchprice_changed
12h agofree402472 msv2yes$0.00520xc8Fc…2Ff0—
19h agofree402174 msv2yes$0.00520xc8Fc…2Ff0—
25h agofree402175 msv2yes$0.00520xc8Fc…2Ff0—
32h agofree402163 msv2yes$0.00520xc8Fc…2Ff0—
39h agofree400456 ms—no——unexpected_status:400status_not_402
45h agofree400156 ms—no——unexpected_status:400status_not_402
2d agofree400247 ms—no——unexpected_status:400status_not_402