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

x402-data-api.sigrunner.workers.dev/chain/block-number

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402-data-api.sigrunner.workers.dev/chain/block-number
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x5765ae06a52dc7a0bb71c36a11db512c7ea9ed10
Declared price (base units)2000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-11-04 08:05 UTC
Catalog-reported calls / payers (30d)8 / 3

2.Probe history

2026-08-262026-11-04
Figure 1. Probe timeline, last 17 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-11-04 06:40 UTCGETpass402423 ms—
2026-11-01 16:40 UTCGETfail402431 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913.
2026-10-30 16:40 UTCGETfail4021554 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913.
2026-10-28 16:40 UTCGETfail402400 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913.
2026-10-27 00:40 UTCGETfail402178 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913.
2026-10-25 06:40 UTCGETfail40244 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913.
2026-10-23 04:40 UTCGETfail40273 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913.
2026-10-21 16:40 UTCGETfail40288 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913.
2026-10-20 10:30 UTCGETfail40217 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-09-26 10:30 UTCGETpass402582 ms—
2026-09-22 11:24 UTCGETpass402112 ms—
2026-09-18 11:24 UTCGETpass40228 ms—
2026-09-15 11:24 UTCGETpass40217 ms—
2026-09-11 11:24 UTCGETpass40217 ms—
2026-09-08 11:24 UTCGETpass40236 ms—
2026-09-03 11:24 UTCGETpass40232 ms—
2026-08-26 10:33 UTCGETfail402426 msaccepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).

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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-27delisted{"status":"active"}{"status":"delisted"}

unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.

5.Dispute this record

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far