x402-factory.com/v1/calendar/politics-us
1.Catalog declaration
| Resource URL | https://x402-factory.com/v1/calendar/politics-us |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xcc42ed39a06b6cf3f484307ef76b88bf56fb305f |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-10-18 16:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 102 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 28 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 142 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 2074 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 49 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 251 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 23 ms | — |
| 2026-10-05 22:40 UTC | GET | pass | 402 | 288 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 253 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 77 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 11 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-10-01 10:31 UTC | GET | pass | 402 | 22 ms | — |
| 2026-09-26 10:30 UTC | GET | pass | 402 | 12 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 49 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 29 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 620 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 11 ms | — |
3.L1 — real purchases
1 of 1 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.
Terms in this table
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 |
|---|---|---|---|---|
| 08-19 12:162026-08-19 12:16 UTC | settled (amount + payee) | 200 | 0x2cfbae4b…fe9a | 1166 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 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/5dcfcca5-6b94-4ec6-9b38-88415e635f12)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.