Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-18 · 2 days ago

402sentinel.com/api/assess/rwa

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://402sentinel.com/api/assess/rwa
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x1a9fa76f5b420e85de147c4419638bebe64d6de5
Declared price (base units)20000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)4 / 1

2.Probe history

2026-08-312026-10-18
Figure 1. Probe timeline, last 24 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-10-18 16:40 UTCPOSTpass402459 ms—
2026-10-17 13:40 UTCPOSTpass4023010 ms—
2026-10-15 21:40 UTCPOSTpass4024957 ms—
2026-10-14 15:40 UTCPOSTpass402808 ms—
2026-10-13 03:40 UTCPOSTpass402722 ms—
2026-10-12 03:40 UTCPOSTpass402941 ms—
2026-10-11 03:40 UTCPOSTpass402789 ms—
2026-10-09 21:40 UTCPOSTpass402783 ms—
2026-10-08 16:40 UTCPOSTpass402280 ms—
2026-10-07 16:40 UTCPOSTpass402820 ms—
2026-10-06 16:40 UTCPOSTpass402392 ms—
2026-10-05 22:40 UTCPOSTpass402273 ms—
2026-10-04 13:40 UTCPOSTpass402327 ms—
2026-10-03 16:40 UTCPOSTpass402454 ms—
2026-10-02 22:40 UTCPOSTpass402502 ms—
2026-10-02 04:40 UTCPOSTpass4021123 ms—
2026-09-27 10:30 UTCPOSTpass402764 ms—
2026-09-22 11:24 UTCPOSTpass402779 ms—
2026-09-18 11:24 UTCPOSTpass402775 ms—
2026-09-16 11:24 UTCPOSTpass402788 ms—
2026-09-12 11:24 UTCPOSTpass402691 ms—
2026-09-08 11:24 UTCPOSTpass402242 ms—
2026-09-03 11:24 UTCPOSTpass402710 ms—
2026-08-31 11:24 UTCPOSTfail402286 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

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