agent402.tools/api/skill/earnings-watch
1.Catalog declaration
| Resource URL | https://agent402.tools/api/skill/earnings-watch |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0 |
| Declared price (base units) | 24000 |
| Catalog status | active |
| First seen / last seen | 2026-09-01 01:03 UTC / 2026-09-27 01:02 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-26 16:40 UTC | POST | fail | 402 | 109 ms | price_mismatch |
| 2026-09-25 22:40 UTC | POST | fail | 402 | 182 ms | price_mismatch |
| 2026-09-25 04:40 UTC | POST | fail | 402 | 194 ms | price_mismatch |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 153 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 191 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 338 ms | — |
| 2026-09-19 11:24 UTC | POST | fail | 402 | 97 ms | price_mismatch |
| 2026-09-17 11:24 UTC | POST | fail | 402 | 86 ms | price_mismatch |
| 2026-09-13 11:24 UTC | POST | fail | 402 | 106 ms | price_mismatch |
| 2026-09-09 11:24 UTC | POST | fail | 402 | 84 ms | price_mismatch |
| 2026-09-06 11:24 UTC | POST | fail | 402 | 117 ms | price_mismatch |
| 2026-09-05 11:24 UTC | POST | fail | 402 | 125 ms | price_mismatch |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-23 12:002026-09-23 12:00 UTC | settled (nonce-bound) | 200 | 0xe4e3b608…9a13 | 8254 ms |
| 24000 units (≈ $0.02 USDC) · L2 match | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/336113fd-b37c-4357-b70d-378e7b835127)4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.