agent402.tools/api/skill/price-monitor
1.Catalog declaration
| Resource URL | https://agent402.tools/api/skill/price-monitor |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0 |
| Declared price (base units) | 21000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 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 | pass | 402 | 100 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 1503 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 125 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 372 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 176 ms | — |
| 2026-09-22 22:40 UTC | POST | fail | 402 | 2102 ms | price_mismatch |
| 2026-09-22 04:40 UTC | POST | fail | 402 | 267 ms | price_mismatch |
| 2026-09-21 13:40 UTC | POST | fail | 402 | 2047 ms | price_mismatch |
| 2026-09-20 16:40 UTC | POST | fail | 402 | 113 ms | price_mismatch |
| 2026-09-20 04:40 UTC | POST | fail | 402 | 564 ms | price_mismatch |
| 2026-09-19 13:40 UTC | POST | fail | 402 | 112 ms | price_mismatch |
| 2026-09-18 16:40 UTC | POST | fail | 402 | 120 ms | price_mismatch |
| 2026-09-17 22:40 UTC | POST | fail | 402 | 189 ms | price_mismatch |
| 2026-09-17 04:40 UTC | POST | fail | 402 | 118 ms | price_mismatch |
| 2026-09-16 16:40 UTC | POST | fail | 402 | 198 ms | price_mismatch |
| 2026-09-15 16:40 UTC | POST | fail | 402 | 111 ms | price_mismatch |
| 2026-09-15 04:40 UTC | POST | fail | 402 | 150 ms | price_mismatch |
| 2026-09-14 13:40 UTC | POST | fail | 402 | 175 ms | price_mismatch |
| 2026-09-13 22:40 UTC | POST | fail | 402 | 193 ms | price_mismatch |
| 2026-09-13 04:40 UTC | POST | fail | 402 | 98 ms | price_mismatch |
| 2026-09-12 16:40 UTC | POST | fail | 402 | 134 ms | price_mismatch |
| 2026-09-11 22:40 UTC | POST | fail | 402 | 211 ms | price_mismatch |
| 2026-09-11 13:40 UTC | POST | fail | 402 | 91 ms | price_mismatch |
| 2026-09-10 23:40 UTC | POST | fail | 402 | 163 ms | price_mismatch |
| 2026-09-10 05:40 UTC | POST | fail | 402 | 139 ms | price_mismatch |
| 2026-09-09 17:40 UTC | POST | fail | 402 | 119 ms | price_mismatch |
| 2026-09-09 05:40 UTC | POST | fail | 402 | 220 ms | price_mismatch |
| 2026-09-08 17:40 UTC | POST | fail | 402 | 865 ms | price_mismatch |
| 2026-09-08 05:40 UTC | POST | fail | 402 | 180 ms | price_mismatch |
| 2026-09-07 14:40 UTC | POST | fail | 402 | 2197 ms | price_mismatch |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 0 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-24 00:012026-09-24 00:01 UTC | settled (nonce-bound)tx from our index | — | 0xc5a1b8af…b82d | 20167 ms |
| 21000 units (≈ $0.02 USDC) · L2 not_checked | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 0 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/25bc49b4-be18-4655-8632-dada8257d07c)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-01 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-24 | delisted | {"status":"active"} | {"status":"delisted"} |
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.