api.x402node.dev/stablecoin/by-chain
1.Catalog declaration
| Resource URL | https://api.x402node.dev/stablecoin/by-chain |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x4466d4a84b7c49a6a094ec6eef4a0712d6dd125e |
| Declared price (base units) | 8000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-14 21:40 UTC | GET | pass | 402 | 243 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 433 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 253 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 1285 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 329 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 88 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 302 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 2041 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 157 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 325 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 770 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 198 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 120 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). 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.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 no_declaration- the listing declares no output schema to check the response against.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-16 00:022026-09-16 00:02 UTC | settled (nonce-bound) | 200 | 0xe709a378…9502 | 1601 ms |
| 8000 units (≈ $0.008 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-08 07:012026-09-08 07:01 UTC | settled (nonce-bound) | 200 | 0xf6c22484…39fd | 1588 ms |
| 8000 units (≈ $0.008 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/39f3be54-6dc1-4f1e-9775-44b9c5203675)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-30 | 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.