Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: withdrawnLast probed: 2026-09-23 · 32 days ago

api.arkm.com/x402/search

Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.arkm.com/x402/search
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x942bd3e3073543c674efc0c378d5bce20f9120c1
Declared price (base units)6000000
Catalog statusdelisted (since 2026-09-24 01:02 UTC)
First seen / last seen2026-08-14 08:39 UTC / 2026-09-23 01:02 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-052026-09-23
Figure 1. Probe timeline, last 30 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-09-23 22:40 UTCPOSTfail403127 msno_402HTTP 403 instead of 402 to an unpaid POST.
2026-09-23 04:40 UTCPOSTfail40375 msno_402HTTP 403 instead of 402 to an unpaid POST.
2026-09-22 13:40 UTCPOSTpass402301 ms—
2026-09-21 16:40 UTCPOSTpass4022026 ms—
2026-09-20 22:40 UTCPOSTpass402138 ms—
2026-09-20 04:40 UTCPOSTpass402125 ms—
2026-09-19 13:40 UTCPOSTpass402155 ms—
2026-09-18 22:40 UTCPOSTpass40279 ms—
2026-09-18 04:40 UTCPOSTpass40237 ms—
2026-09-17 13:40 UTCPOSTpass4022015 ms—
2026-09-16 22:40 UTCPOSTpass402547 ms—
2026-09-15 22:40 UTCPOSTpass402180 ms—
2026-09-15 04:40 UTCPOSTpass40263 ms—
2026-09-14 16:40 UTCPOSTpass40252 ms—
2026-09-13 22:40 UTCPOSTpass402120 ms—
2026-09-13 13:40 UTCPOSTpass402103 ms—
2026-09-12 16:40 UTCPOSTpass40263 ms—
2026-09-12 04:40 UTCPOSTpass402301 ms—
2026-09-11 16:40 UTCPOSTpass402175 ms—
2026-09-10 23:40 UTCPOSTpass40247 ms—
2026-09-10 14:40 UTCPOSTpass40296 ms—
2026-09-09 23:40 UTCPOSTpass402152 ms—
2026-09-09 14:40 UTCPOSTpass40286 ms—
2026-09-08 17:40 UTCPOSTpass402182 ms—
2026-09-08 05:40 UTCPOSTpass40247 ms—
2026-09-07 17:40 UTCPOSTpass40251 ms—
2026-09-07 05:40 UTCPOSTpass40245 ms—
2026-09-06 17:40 UTCPOSTpass40237 ms—
2026-09-06 05:40 UTCPOSTpass40254 ms—
2026-09-05 17:40 UTCPOSTpass40237 ms—

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-24delisted{"status":"active"}{"status":"delisted"}
2026-08-26relisted{"status":"delisted"}{"status":"active"}
2026-08-24delisted{"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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. 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