Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-23 · 13 days ago
api.arkm.com/x402/counterparties/address
1.Catalog declaration
| Resource URL | https://api.arkm.com/x402/counterparties/address |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x942bd3e3073543c674efc0c378d5bce20f9120c1 |
| Declared price (base units) | 10000000 |
| Catalog status | delisted (since 2026-09-24 01:02 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-23 01:02 UTC |
| Catalog-reported calls / payers (30d) | 5 / 1 |
2.Probe history
2026-09-052026-09-23
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-23 16:40 UTC | POST | fail | 403 | 26 ms | no_402HTTP 403 instead of 402 to an unpaid POST. |
| 2026-09-22 22:40 UTC | POST | fail | 403 | 232 ms | no_402HTTP 403 instead of 402 to an unpaid POST. |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 148 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 114 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 111 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 72 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 133 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 34 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 33 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 95 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 308 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 534 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 727 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 76 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 77 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 55 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 219 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 2029 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 71 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 280 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 320 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 134 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 2175 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 326 ms | — |
| 2026-09-07 23:40 UTC | POST | pass | 402 | 106 ms | — |
| 2026-09-07 14:40 UTC | POST | pass | 402 | 267 ms | — |
| 2026-09-06 23:40 UTC | POST | pass | 402 | 74 ms | — |
| 2026-09-06 14:40 UTC | POST | pass | 402 | 332 ms | — |
| 2026-09-05 23:40 UTC | POST | pass | 402 | 291 ms | — |
| 2026-09-05 14:40 UTC | POST | pass | 402 | 33 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-24 | 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.