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

api.hergertsynthora.com/v1/ecb-macro

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://api.hergertsynthora.com/v1/ecb-macro
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0xef879bfd6c4accb8f795136de90246e1ec245e06
Declared price (base units)	30000
Catalog status	active
First seen / last seen	2026-08-19 01:34 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)	3 / 3

2.Probe history

2026-09-042026-09-26

Figure 1. Probe timeline, last 16 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-26 16:40 UTC	POST	pass	402	486 ms	—
2026-09-25 22:40 UTC	POST	pass	402	327 ms	—
2026-09-25 04:40 UTC	POST	pass	402	549 ms	—
2026-09-24 13:40 UTC	POST	pass	402	2131 ms	—
2026-09-23 16:40 UTC	POST	fail	402	638 ms	price_mismatch
2026-09-22 22:40 UTC	POST	fail	402	374 ms	price_mismatch
2026-09-22 04:40 UTC	POST	fail	402	579 ms	price_mismatch
2026-09-21 13:40 UTC	POST	fail	402	348 ms	price_mismatch
2026-09-20 16:40 UTC	POST	fail	402	181 ms	price_mismatch
2026-09-19 22:40 UTC	POST	fail	402	123 ms	price_mismatch
2026-09-19 11:24 UTC	POST	fail	402	340 ms	price_mismatch
2026-09-17 11:24 UTC	POST	fail	402	243 ms	price_mismatch
2026-09-12 11:24 UTC	POST	fail	402	359 ms	price_mismatch
2026-09-09 11:24 UTC	POST	fail	402	109 ms	price_mismatch
2026-09-05 11:24 UTC	POST	fail	402	405 ms	price_mismatch
2026-09-04 11:24 UTC	POST	fail	402	271 ms	price_mismatch

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-24 18:012026-09-24 18:01 UTC	settled (nonce-bound)	200	0x8bc58364…4e3d	3211 ms
30000 units (≈ $0.03 USDC) · L2 no_declaration

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/cdb9fe21-b52e-4a67-80e9-59bd0b6b8681.svg)](https://vet402.com/observatory/e/cdb9fe21-b52e-4a67-80e9-59bd0b6b8681)

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.