Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-13 · today

heb-utils-x402.hebutils-api.workers.dev/base-nonce

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://heb-utils-x402.hebutils-api.workers.dev/base-nonce
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x1cd76fe5f38ae5b2785962ee5a3799e846e9fa52
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-10-11 01:02 UTC / 2026-10-13 01:02 UTC
Catalog-reported calls / payers (30d)2 / 1

2.Probe history

2026-10-122026-10-13
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 atMethodVerdictHTTPLatencyReason
2026-10-13 10:30 UTCGETpass40274 ms—
2026-10-12 10:33 UTCGETfail402266 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 1000 of 0x8335…2913.

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

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.

20–2,000 characters · 0 so far