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

76.13.79.47.nip.io/token-signal-x402/v1/x402-market-feed

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://76.13.79.47.nip.io/token-signal-x402/v1/x402-market-feed
Source	cdp_bazaar
Declared method	GET
Network	eip155:8453
Receiving address	0x10333d09dd1f5ebd8b8bd83f74a9d99c7b88129f
Declared price (base units)	1000
Catalog status	active
First seen / last seen	2026-08-14 08:39 UTC / 2026-09-08 01:03 UTC
Catalog-reported calls / payers (30d)	107 / 2

2.Probe history

2026-08-162026-09-07

Figure 1. Probe timeline, last 13 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-07 23:40 UTC	GET	pass	402	849 ms	—
2026-09-07 05:40 UTC	GET	fail	402	1398 ms	price_mismatch
2026-09-06 17:40 UTC	GET	fail	402	1981 ms	price_mismatch
2026-09-06 05:40 UTC	GET	fail	402	906 ms	price_mismatch
2026-09-05 17:40 UTC	GET	fail	402	883 ms	price_mismatch
2026-09-05 05:40 UTC	GET	fail	402	1024 ms	price_mismatch
2026-09-04 17:40 UTC	GET	fail	402	858 ms	price_mismatch
2026-09-04 05:40 UTC	GET	fail	402	963 ms	price_mismatch
2026-09-03 17:40 UTC	GET	fail	402	746 ms	price_mismatch
2026-09-03 05:40 UTC	GET	fail	402	873 ms	price_mismatch
2026-09-02 17:40 UTC	GET	fail	402	1150 ms	price_mismatch
2026-09-02 11:25 UTC	GET	fail	402	743 ms	price_mismatch
2026-08-16 10:39 UTC	GET	fail	402	831 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-08 01:002026-09-08 01:00 UTC	settled (nonce-bound)	200	0x26b335db…33c0	4194 ms
1000 units (≈ $0.001 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/1c0cb202-ab30-45b1-9429-526510af84be.svg)](https://vet402.com/observatory/e/1c0cb202-ab30-45b1-9429-526510af84be)

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.