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

api.resetparatodos.com/x402/v1/uk/company/verify

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://api.resetparatodos.com/x402/v1/uk/company/verify
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0x54bea1e6f70437085b85892a0e7cd6f09ce8c22f
Declared price (base units)	30000
Catalog status	active
First seen / last seen	2026-08-26 01:39 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)	2 / 2

2.Probe history

2026-09-022026-09-04

Figure 1. Probe timeline, last 6 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-04 17:40 UTC	POST	pass	402	366 ms	—
2026-09-04 05:40 UTC	POST	pass	402	508 ms	—
2026-09-03 17:40 UTC	POST	pass	402	364 ms	—
2026-09-03 05:40 UTC	POST	pass	402	545 ms	—
2026-09-02 23:40 UTC	POST	pass	402	475 ms	—
2026-09-02 14:40 UTC	POST	pass	402	377 ms	—

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 4xx or 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 at	Result	HTTP	Receipt (tx)	Latency
09-04 09:252026-09-04 09:25 UTC	settle_failed	400	—	4153 ms
30000 units (≈ $0.03 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.