x402-factory.com/v1/evergreen/nba-finals-winner
1.Catalog declaration
| Resource URL | https://x402-factory.com/v1/evergreen/nba-finals-winner |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xcc42ed39a06b6cf3f484307ef76b88bf56fb305f |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-15 12:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 302 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 208 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 51 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 68 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 76 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 1952 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 46 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 53 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 223 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 23 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 1801 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 54 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 269 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 34 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 28 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 69 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 10 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 29 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 12 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 67 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.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 match- the response had the 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-16 00:012026-09-16 00:01 UTC | settled (nonce-bound) | 200 | 0xc9e564e7…5b2b | 1369 ms |
| 20000 units (≈ $0.02 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-26 12:362026-08-26 12:36 UTC | settled (amount + payee) | 200 | 0x9db406e0…480b | 11925 ms |
| 20000 units (≈ $0.02 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-19 12:152026-08-19 12:15 UTC | settled (amount + payee) | 200 | 0xf75927a2…7025 | 2128 ms |
| 20000 units (≈ $0.02 USDC) · L2 matchWhose 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/de519292-d785-4bc0-a751-0e522d0c9f49)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-08 | 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.