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

contextiq.trango-compute.com/api/v1/policy-check/x402-v2

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://contextiq.trango-compute.com/api/v1/policy-check/x402-v2
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0x4eba5ea3cf0f3fc307099317e17e54390f7a4c58
Declared price (base units)	20000
Catalog status	active
First seen / last seen	2026-09-12 01:03 UTC / 2026-09-13 01:03 UTC
Catalog-reported calls / payers (30d)	6 / 2

2.Probe history

2026-09-12

Figure 1. Probe timeline, last 2 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-09-12 22:40 UTC	POST	pass	402	291 ms	—
2026-09-12 11:24 UTC	POST	pass	402	247 ms	—

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt, and 0 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 of those settled attempts answered 4xx, and we hold them as inconclusive rather than counting them against this seller. A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with an empty JSON body and no API key of the seller's. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).

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-12 12:072026-09-12 12:07 UTC	settled (nonce-bound)	400	0xb67b3315…14eb	1146 ms
20000 units (≈ $0.02 USDC) · L2 not_checked

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 0 delivered · 1 inconclusive 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/2604b7c7-3c98-4640-88e3-374a25fd8164.svg)](https://vet402.com/observatory/e/2604b7c7-3c98-4640-88e3-374a25fd8164)

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.