402cron.com/buy/trial
1.Catalog declaration
| Resource URL | https://402cron.com/buy/trial |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x8e37022edcf0f21cf3c9f93fee9d4d32519f36f4 |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-09-10 01:03 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 8 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 160 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 276 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 1986 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 238 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 2121 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 1906 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 2138 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 244 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 230 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 151 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 102 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 87 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 168 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 15 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-24 12:022026-09-24 12:02 UTC | settled (nonce-bound)tx from our index | 200 | 0xdfb920f5…e06d | 3290 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-17 18:022026-09-17 18:02 UTC | settled (nonce-bound)tx from our index | 200 | 0xf7d84754…5e6d | 3564 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-10 19:002026-09-10 19:00 UTC | settled (nonce-bound)tx from our index | 200 | 0x920854db…97f6 | 3578 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose 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/066686c3-2ac5-4ea3-b71e-43e87c248d5b)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-10T19:00:19Z (UTC). The form starts with that time; add what you saw instead.