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

cron402-api.user-defaults.workers.dev/v1/crons/topup/100

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://cron402-api.user-defaults.workers.dev/v1/crons/topup/100
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0xc7d7b6d856ab058a9373e61cf46a85d1f73da695
Declared price (base units)	800000
Catalog status	active
First seen / last seen	2026-09-11 01:03 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)	2 / 1

2.Probe history

2026-09-112026-09-26

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-26 10:30 UTC	POST	fail	402	298 ms	metadata_mismatch
2026-09-22 11:24 UTC	POST	fail	402	175 ms	metadata_mismatch
2026-09-18 11:24 UTC	POST	fail	402	356 ms	metadata_mismatch
2026-09-15 11:24 UTC	POST	fail	402	211 ms	metadata_mismatch
2026-09-12 11:24 UTC	POST	fail	402	662 ms	metadata_mismatch
2026-09-11 11:24 UTC	POST	fail	402	77 ms	metadata_mismatch

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

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.