Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-16 · today
vet402Back to the registerMethodology

api.hergertsynthora.com/v1/air-quality

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.hergertsynthora.com/v1/air-quality
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xef879bfd6c4accb8f795136de90246e1ec245e06
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-19 01:34 UTC / 2026-09-16 01:03 UTC
Catalog-reported calls / payers (30d)5 / 4

2.Probe history

2026-09-042026-09-16
Figure 1. Probe timeline, last 22 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 atMethodVerdictHTTPLatencyReason
2026-09-16 13:40 UTCPOSTpass402371 ms—
2026-09-15 16:40 UTCPOSTpass402582 ms—
2026-09-14 22:40 UTCPOSTfail402381 msprice_mismatch
2026-09-14 04:40 UTCPOSTfail402443 msprice_mismatch
2026-09-13 16:40 UTCPOSTfail402312 msprice_mismatch
2026-09-13 04:40 UTCPOSTfail402411 msprice_mismatch
2026-09-12 13:40 UTCPOSTfail402309 msprice_mismatch
2026-09-11 22:40 UTCPOSTfail402411 msprice_mismatch
2026-09-11 04:40 UTCPOSTfail402473 msprice_mismatch
2026-09-10 17:40 UTCPOSTfail402337 msprice_mismatch
2026-09-10 05:40 UTCPOSTfail402369 msprice_mismatch
2026-09-09 14:40 UTCPOSTfail4021545 msprice_mismatch
2026-09-08 23:40 UTCPOSTfail402488 msprice_mismatch
2026-09-08 14:40 UTCPOSTfail402340 msprice_mismatch
2026-09-07 23:40 UTCPOSTfail402411 msprice_mismatch
2026-09-07 14:40 UTCPOSTfail402562 msprice_mismatch
2026-09-06 23:40 UTCPOSTfail4022408 msprice_mismatch
2026-09-06 14:40 UTCPOSTfail402392 msprice_mismatch
2026-09-05 17:40 UTCPOSTfail402519 msprice_mismatch
2026-09-05 05:40 UTCPOSTfail4021007 msprice_mismatch
2026-09-04 17:40 UTCPOSTfail402305 msprice_mismatch
2026-09-04 11:24 UTCPOSTfail402325 msprice_mismatch

3.L1 — real purchases

0 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.

0/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 atResultHTTPReceipt (tx)Latency
09-15 18:00settle_failed402—6819 ms
10000 units (≈ $0.01 USDC) · L2 not_checked

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint.

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.