Paywary

Leaderboard / trust-agent.io / endpoint

GET https://trust-agent.io/v1/endpoint/screen

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 11 probes in the last 7 days.
Category
x402 tooling by llm, confidence 60%
Latest quote
$0.005 on Base to 0x6121…e6BB
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
43m ago
Next probe
2026-11-19 01:41 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
9w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0050x6121…e6BBdefaultyes3h 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
43h agox402 tooling60%llmv1claude-haiku-5-5: The endpoint inspects x402 payment challenges and screens payout wallets, which fits x402 payment-header tooling, but it also performs OFAC sanctions screening and returns a risk verdict, so compliance is a plausible alternative. The x402_meta category fits best because the core function is analysing an x402 endpoint's payment requirements before payment.
47h agox402 tooling60%rulesv1rule x402_meta matched "x402 endpoint" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
43m agofree402368 msv2yes$0.0050x6121…e6BB—
8h agofree402150 msv2yes$0.0050x6121…e6BB—
14h agofree402112 msv2yes$0.0050x6121…e6BB—
20h agofree402240 msv2yes$0.0050x6121…e6BB—
27h agofree402170 msv2yes$0.0050x6121…e6BB—
33h agofree402261 msv2yes$0.0050x6121…e6BB—
40h agofree402251 msv2yes$0.0050x6121…e6BB—
46h agofree402118 msv2yes$0.0050x6121…e6BB—
2d agofree402132 msv2yes$0.0050x6121…e6BB—
2d agofree402134 msv2yes$0.0050x6121…e6BB—
3d agofree402270 msv2yes$0.0050x6121…e6BB—