Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-17 · today

x402.creative-tim.com/api/shadcn-block

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://x402.creative-tim.com/api/shadcn-block
Source	cdp_bazaar
Declared method	HEAD
Network	eip155:8453
Receiving address	0x45ac00db8bdd4b837abbbf75888cbdfe6b6d8943
Declared price (base units)	10000
Catalog status	active
First seen / last seen	2026-08-14 08:52 UTC / 2026-09-17 12:35 UTC
Catalog-reported calls / payers (30d)	4 / 1

2.Probe history

2026-08-292026-09-17

Figure 1. Probe timeline, last 9 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 at	Method	Verdict	HTTP	Latency	Reason
2026-09-17 16:40 UTC	HEAD	pass	402	135 ms	—
2026-09-17 04:40 UTC	HEAD	pass	402	152 ms	—
2026-09-04 17:40 UTC	HEAD	pass	402	275 ms	—
2026-09-04 05:40 UTC	HEAD	pass	402	225 ms	—
2026-09-03 23:40 UTC	HEAD	pass	402	196 ms	—
2026-09-03 14:40 UTC	HEAD	fail	503	154 ms	no_402
2026-09-02 23:40 UTC	HEAD	pass	402	129 ms	—
2026-09-02 14:40 UTC	HEAD	pass	402	381 ms	—
2026-08-29 11:24 UTC	HEAD	fail	402	75 ms	accepts_invalid

3.L1 — real purchases

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

1/1

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 at	Result	HTTP	Receipt (tx)	Latency
09-17 06:012026-09-17 06:01 UTC	settled (nonce-bound)	200	0x40a3c1eb…a1fc	2460 ms
10000 units (≈ $0.01 USDC) · L2 mismatch

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.

[![vet402 receipt](https://vet402.com/api/badge/endpoint/090d38e3-fe8d-489b-ba75-e46d4e0577d4.svg)](https://vet402.com/observatory/e/090d38e3-fe8d-489b-ba75-e46d4e0577d4)

4.Catalog listing events

Catalog listing events, newest first
Detected on	Event	Before	After
2026-09-17	relisted	`{"status":"delisted"}`	`{"status":"active"}`
2026-09-05	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.