Leaderboard / agent402.tools / endpoint
POST https://agent402.tools/api/feedback
Scores measure reliability and honesty, not output quality.
- 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
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | eip155:42220 | 0xcebA…118C | 1000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | Polygon | 0x3c49…3359 | 1000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | Base | 0x8335…2913 | $0.001 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | Avalanche | 0xB97E…8a6E | 1000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:10 | 0x0b2C…Ff85 | 2000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:4663 | 0x5fc5…d168 | 10000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | Arbitrum | 0xaf88…5831 | 1000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:1329 | 0xe15f…2392 | 1000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:57073 | 0x2D27…EAEd | 1000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:143 | 0x7547…b603 | 1000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:5042 | 0x3600…0000 | 1000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| payai | exact | Base | 0x8335…2913 | $0.001 | 0xaBF4…a9D0 | default | yes | 5h ago |
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 40h ago | description_changed | 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 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 ago | description_changed | 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 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 ago | description_changed | 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 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 ago | price_changed | 5000 | 10000 |
| 40h ago | description_changed | 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 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 ago | description_changed | 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 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 ago | description_changed | 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 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 ago | description_changed | 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 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 ago | description_changed | 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 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 ago | description_changed | 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 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 ago | description_changed | 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 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.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 39h ago | x402 tooling | 80% | llm | v1 | claude-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 ago | Chain read | 60% | rules | v1 | rule chain_read matched "in:tx" in metadata |
| 45h ago | x402 tooling | 60% | llm | v1 | claude-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 ago | Chain read | 60% | rules | v1 | rule chain_read matched "in:tx" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 56 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 9h ago | free | 402 | 28 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 15h ago | free | 402 | 305 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 22h ago | free | 402 | 123 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 29h ago | free | 402 | 105 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 35h ago | free | 402 | 893 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 41h ago | free | 402 | 410 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 2d ago | free | 402 | 364 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 2d ago | free | 402 | 84 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 3d ago | free | 402 | 40 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 3d ago | free | 402 | 585 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 3d ago | free | 402 | 53 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |
| 3d ago | free | 402 | 41 ms | v2 | yes | $0.001 | 0xaBF4…a9D0 | — |