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

x402.devvizion.com/v0/bounty-radar

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://x402.devvizion.com/v0/bounty-radar
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0xe79e7fa7ce7259c46f9b127b837d2907bb036f95
Declared price (base units)	15000
Catalog status	active
First seen / last seen	2026-08-14 08:39 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)	5 / 3

2.Probe history

2026-08-152026-09-04

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-04 23:40 UTC	POST	pass	402	2103 ms	—
2026-09-04 14:40 UTC	POST	pass	402	378 ms	—
2026-09-04 05:40 UTC	POST	pass	402	446 ms	—
2026-09-03 17:40 UTC	POST	pass	402	258 ms	—
2026-09-03 05:40 UTC	POST	pass	402	212 ms	—
2026-09-02 17:40 UTC	POST	pass	402	292 ms	—
2026-09-02 05:40 UTC	POST	pass	402	209 ms	—
2026-09-01 23:40 UTC	POST	pass	402	222 ms	—
2026-08-15 10:42 UTC	POST	pass	402	175 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 4xx or 5xx counts as settled and not as delivered — definitions.

3/3

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
08-30 12:082026-08-30 12:08 UTC	settled (amount + payee)	200	0xc5bc0c30…2de2	8899 ms
15000 units (≈ $0.01 USDC) · L2 no_declaration
08-23 12:432026-08-23 12:43 UTC	settled (amount + payee)	200	0x12c43e3f…22a4	2204 ms
15000 units (≈ $0.01 USDC) · L2 no_declaration
08-15 12:482026-08-15 12:48 UTC	settled (amount + payee)	200	0x2f101243…00a1	2099 ms
15000 units (≈ $0.01 USDC) · L2 no_declaration

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 states a measurement, not a rating.

[![vet402 receipt](https://vet402.com/api/badge/endpoint/4e1d7aff-6763-4594-b0ab-87ff5abeeb94.svg)](https://vet402.com/observatory/e/4e1d7aff-6763-4594-b0ab-87ff5abeeb94)

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.