Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-02 · 2 days ago

api.sirenic.eu/v1/eu/entreprise/GB/:company_number/comptes/:date_cloture

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://api.sirenic.eu/v1/eu/entreprise/GB/:company_number/comptes/:date_cloture
Source	cdp_bazaar
Declared method	GET
Network	eip155:8453
Receiving address	0x76a672eee56d29d475b0715cc03b8c99d70ec8a2
Declared price (base units)	50000
Catalog status	active
First seen / last seen	2026-08-14 08:39 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)	8 / 1

2.Probe history

2026-08-172026-09-02

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-02 05:40 UTC	GET	pass	402	157 ms	—
2026-08-17 10:39 UTC	GET	pass	402	158 ms	—

3.L1 — real purchases

0 of 2 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 4xx or 5xx counts as settled and not as delivered — definitions.

0/2

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-24 23:372026-08-24 23:37 UTC	settle_failed	400	—	424 ms
50000 units (≈ $0.05 USDC) · L2 not_checked
08-17 12:482026-08-17 12:48 UTC	settle_failed	400	—	769 ms
50000 units (≈ $0.05 USDC) · L2 not_checked

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.