Paywary

Leaderboard / agent402.tools / endpoint

POST https://agent402.tools/api/feedback

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
x402 tooling by llm, confidence 80%
Latest quote
$0.001 on Base to 0xaBF4…a9D0
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
2h ago
Next probe
2026-11-19 14:49 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
cdpexacteip155:422200xcebA…118C10000xaBF4…a9D0defaultyes5h ago
cdpexactPolygon0x3c49…335910000xaBF4…a9D0defaultyes5h ago
cdpexactBase0x8335…2913$0.0010xaBF4…a9D0defaultyes5h ago
cdpexactAvalanche0xB97E…8a6E10000xaBF4…a9D0defaultyes5h ago
cdpexacteip155:100x0b2C…Ff8520000xaBF4…a9D0defaultyes5h ago
cdpexacteip155:46630x5fc5…d168100000xaBF4…a9D0defaultyes5h ago
cdpexactArbitrum0xaf88…583110000xaBF4…a9D0defaultyes5h ago
cdpexacteip155:13290xe15f…239210000xaBF4…a9D0defaultyes5h ago
cdpexacteip155:570730x2D27…EAEd10000xaBF4…a9D0defaultyes5h ago
cdpexacteip155:1430x7547…b60310000xaBF4…a9D0defaultyes5h ago
cdpexacteip155:50420x3600…000010000xaBF4…a9D0defaultyes5h ago
payaiexactBase0x8335…2913$0.0010xaBF4…a9D0defaultyes5h ago

Listing changes

WhenEventFromTo
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.
40h agoprice_changed500010000
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.
40h agodescription_changedTell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call can write it - so a rating here is always a real customer about a real purchase. One verdict per settlement transaction (sending another replaces yours, it never stacks).Tell this server whether a call you paid for delivered what it promised. Bound to the receipt: give it the settlement transaction from that call's PAYMENT-RESPONSE (or Payment-Receipt) header and a verdict of "good" or "bad", and only the wallet the ledger records as having paid for that exact call.

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
39h agox402 tooling80%llmv1claude-haiku-5-5: The endpoint lets a payer rate a paid x402 call using its settlement receipt, which is payment-protocol reputation tooling rather than a commercial service, so x402_meta fits best. It is not a commerce or compliance endpoint.
39h agoChain read60%rulesv1rule chain_read matched "in:tx" in metadata
45h agox402 tooling60%llmv1claude-haiku-5-5: The endpoint lets a paying customer submit a good/bad rating bound to a settlement receipt, which is reputation/feedback infrastructure for x402 calls. It is not a commerce credit or listing, so x402_meta fits best, though it could arguably be seen as reputation tooling outside the listed categories.
3d agoChain read60%rulesv1rule chain_read matched "in:tx" in metadata

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
2h agofree40256 msv2yes$0.0010xaBF4…a9D0—
9h agofree40228 msv2yes$0.0010xaBF4…a9D0—
15h agofree402305 msv2yes$0.0010xaBF4…a9D0—
22h agofree402123 msv2yes$0.0010xaBF4…a9D0—
29h agofree402105 msv2yes$0.0010xaBF4…a9D0—
35h agofree402893 msv2yes$0.0010xaBF4…a9D0—
41h agofree402410 msv2yes$0.0010xaBF4…a9D0—
2d agofree402364 msv2yes$0.0010xaBF4…a9D0—
2d agofree40284 msv2yes$0.0010xaBF4…a9D0—
3d agofree40240 msv2yes$0.0010xaBF4…a9D0—
3d agofree402585 msv2yes$0.0010xaBF4…a9D0—
3d agofree40253 msv2yes$0.0010xaBF4…a9D0—
3d agofree40241 msv2yes$0.0010xaBF4…a9D0—