x402-factory.com/v1/evergreen/presidential-election-winner-party
1.Catalog declaration
| Resource URL | https://x402-factory.com/v1/evergreen/presidential-election-winner-party |
| 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-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 15 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 124 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 147 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 409 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 550 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 20 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 19 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 322 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 15 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 41 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 94 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 587 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 65 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 2092 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 11 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 40 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 19 ms | — |
| 2026-09-09 14:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
3.L1 — real purchases
3 of 4 paid attempts settled on-chain, and 1 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.
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).
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).
settle_failed- vet402 signed a payment and got no settlement receipt back.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-11 01:022026-09-11 01:02 UTC | settled (nonce-bound)tx from our index | — | 0x0127f693…895c | 20119 ms |
| 20000 units (≈ $0.02 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 08-28 12:192026-08-28 12:19 UTC | settled (amount + payee)tx from our index | — | 0xa101956e…c651 | 20199 ms |
| 20000 units (≈ $0.02 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 08-21 12:202026-08-21 12:20 UTC | settle_failed | — | — | 20237 ms |
| 20000 units (≈ $0.02 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 08-14 10:052026-08-14 10:05 UTC | settled (amount + payee) | 200 | 0x0ed0b8c7…c680 | 6231 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/4 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/666dcff7-4836-4063-af6d-89bdb9cd3bcc)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-08-28T12:19:04Z (UTC). The form starts with that time; add what you saw instead.