Paywary

Leaderboard / agentshield.live / endpoint

POST https://agentshield.live/invoice

Scores measure reliability and honesty, not output quality.

94Payconfidence: high
  • Listed only 3 days ago; new listings earn trust over 30 days.
  • Answered all 13 probes in the last 7 days.
Category
Utility by rules, confidence 90%
Latest quote
$0.03 on Base to 0xC87e…25AE
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
37m ago
Next probe
2026-11-19 14:38 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
11w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.030xC87e…25AEdefaultyes3h ago

Listing changes

WhenEventFromTo
29h agodescription_changedVerify before an invoice is sent or paid. One call checks net + VAT = gross, the VAT amount against the given or standard country rate, the IBAN checksum, the VAT id (German checksum or EU format), the date and the number, and flags the German 250 euro small-invoice rule. Returns ok plus each failed field. Not an XRechnung schema validation. Send the fields as a JSON body so they do not appear in URLs or proxy logs.Call before you send or pay an invoice: check that net + VAT equals gross, that VAT matches the stated or standard country rate, plus IBAN and VAT-id format. Returns ok and failed fields. Not an XRechnung or Peppol schema check. For a receipt photo use /lines, not this route. Send the fields as a JSON body so they do not appear in URLs or proxy logs.

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
28h agoUtility90%rulesv1rule utility matched "iban" in description
3d agoUtility90%rulesv1rule utility matched "iban" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
37m agofree402150 msv2yes$0.030xC87e…25AE—
7h agofree402152 msv2yes$0.030xC87e…25AE—
13h agofree402150 msv2yes$0.030xC87e…25AE—
20h agofree402154 msv2yes$0.030xC87e…25AE—
27h agofree402150 msv2yes$0.030xC87e…25AE—
33h agofree402151 msv2yes$0.030xC87e…25AE—
39h agofree402162 msv2yes$0.030xC87e…25AE—
46h agofree402160 msv2yes$0.030xC87e…25AE—
2d agofree402164 msv2yes$0.030xC87e…25AE—
2d agofree402571 msv2yes$0.030xC87e…25AE—
3d agofree402152 msv2yes$0.030xC87e…25AE—
3d agofree402462 msv2yes$0.030xC87e…25AE—
3d agofree402152 msv2yes$0.030xC87e…25AE—