Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-18 · 2 days ago
tools.halowerk.com/v1/x402/radar
1.Catalog declaration
| Resource URL | https://tools.halowerk.com/v1/x402/radar |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e |
| Declared price (base units) | 8000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
2026-08-252026-10-18
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 22:40 UTC | POST | pass | 402 | 374 ms | — |
| 2026-10-17 16:40 UTC | POST | pass | 402 | 848 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 328 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 327 ms | — |
| 2026-10-13 10:30 UTC | POST | pass | 402 | 349 ms | — |
| 2026-09-15 11:24 UTC | POST | pass | 402 | 354 ms | — |
| 2026-09-11 11:24 UTC | POST | pass | 402 | 342 ms | — |
| 2026-09-08 11:24 UTC | POST | pass | 402 | 419 ms | — |
| 2026-09-03 11:24 UTC | POST | pass | 402 | 492 ms | — |
| 2026-08-25 10:47 UTC | POST | fail | 402 | 335 ms | accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-07 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-16 | delisted | {"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
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.