x402.coinstats.app/news/sources
1.Catalog declaration
| Resource URL | https://x402.coinstats.app/news/sources |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xa2ad8183209e5d2f7f0d8f995f5601a0bb5100c7 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 293 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 427 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 292 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 192 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 821 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 237 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 494 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 336 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 69 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 41 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 467 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 391 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 39 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 198 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 189 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 174 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 1821 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 243 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 645 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 246 ms | — |
| 2026-09-09 17:40 UTC | GET | fail | 402 | 275 ms | metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 239 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 mismatch- the response lacked fields the listing's output schema declares.
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-22 12:102026-09-22 12:10 UTC | settled (nonce-bound) | 200 | 0x4b9a281e…d09f | 1553 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-12 00:002026-09-12 00:00 UTC | settled (nonce-bound) | 200 | 0xa60948e3…f970 | 1133 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-04 12:092026-09-04 12:09 UTC | settled (nonce-bound) | 200 | 0x067bc83d…42e3 | 1707 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/740e6d11-379d-45b2-b849-70f52d80c7ed)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.
About the purchase at 2026-09-12T00:00:54Z (UTC). The form starts with that time; add what you saw instead.