Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-28 · 1 day ago
vet402Back to the registerMethodology

holidays.use.x402atlas.com/check

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://holidays.use.x402atlas.com/check
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x8c128f1ee62bb5e47867cfbae2ad89be325df1b2
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC
Catalog-reported calls / payers (30d)9 / 7

2.Probe history

2026-09-092026-09-28
Figure 1. Probe timeline, last 30 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-28 22:40 UTCGETpass40227 ms—
2026-09-28 04:40 UTCGETpass402236 ms—
2026-09-27 13:40 UTCGETpass402299 ms—
2026-09-26 16:40 UTCGETpass402200 ms—
2026-09-25 22:40 UTCGETpass40218 ms—
2026-09-25 04:40 UTCGETpass402114 ms—
2026-09-24 13:40 UTCGETpass40210 ms—
2026-09-23 16:40 UTCGETpass40229 ms—
2026-09-22 22:40 UTCGETpass40213 ms—
2026-09-22 04:40 UTCGETpass402152 ms—
2026-09-21 16:40 UTCGETpass402257 ms—
2026-09-20 22:40 UTCGETpass4022058 ms—
2026-09-20 04:40 UTCGETpass40280 ms—
2026-09-19 13:40 UTCGETpass402212 ms—
2026-09-18 16:40 UTCGETpass4027 ms—
2026-09-17 22:40 UTCGETpass402186 ms—
2026-09-17 13:40 UTCGETpass40288 ms—
2026-09-16 16:40 UTCGETpass402537 ms—
2026-09-15 16:40 UTCGETpass40212 ms—
2026-09-15 04:40 UTCGETpass402227 ms—
2026-09-14 13:40 UTCGETpass402153 ms—
2026-09-13 22:40 UTCGETpass40270 ms—
2026-09-13 04:40 UTCGETpass402163 ms—
2026-09-12 16:40 UTCGETpass40239 ms—
2026-09-12 04:40 UTCGETpass40296 ms—
2026-09-11 13:40 UTCGETpass402106 ms—
2026-09-10 23:40 UTCGETpass40277 ms—
2026-09-10 14:40 UTCGETpass402139 ms—
2026-09-09 17:40 UTCGETpass40257 ms—
2026-09-09 05:40 UTCGETpass40297 ms—

3.L1 — real purchases

5 of 5 paid attempts settled with a receipt, and 5 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.

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).
5/5
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.
L1 purchase history, newest first
Attempted atResultHTTPReceipt (tx)Latency
09-16 12:09settled (nonce-bound)2000xb43af744…fa0c1399 ms
5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered)
09-10 01:00settled (nonce-bound)2000x1f9a5058…e4621452 ms
5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered)
08-31 12:08settled (amount + payee)2000x54061401…ebe31829 ms
5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered)
08-24 23:35settled (amount + payee)2000x89602ff6…73561277 ms
5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered)
08-15 12:48settled (amount + payee)2000x5ca876ee…1db7940 ms
5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 5/5 settled · 5 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.

vet402: 5 of 5 paid attempts settled with an on-chain receipt, and 5 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (holidays.use.x402atlas.com · measured 2026-09-16)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/6ce35176-e18f-4bb2-8cf8-3fdc3d92e50c.svg)](https://vet402.com/observatory/e/6ce35176-e18f-4bb2-8cf8-3fdc3d92e50c)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

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-16T12:09:37Z (UTC). The form starts with that time; add what you saw instead.