apexrunner.ai/signals/cross-asset-contagion
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
| Resource URL | https://apexrunner.ai/signals/cross-asset-contagion |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x8d0663bbb967ebf1c047405a888ddf865f3e8854 |
| Declared price (base units) | 7000 |
| Catalog status | delisted (since 2026-10-06 01:01 UTC) |
| First seen / last seen | 2026-09-09 01:03 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-05 22:40 UTC | GET | fail | 410 | 1382 ms | no_402HTTP 410 instead of 402 to an unpaid GET. |
| 2026-10-04 16:40 UTC | GET | fail | 410 | 47 ms | no_402HTTP 410 instead of 402 to an unpaid GET. |
| 2026-10-03 22:40 UTC | GET | fail | 410 | 212 ms | no_402HTTP 410 instead of 402 to an unpaid GET. |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 941 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 361 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 198 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 495 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 162 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 419 ms | — |
| 2026-09-27 10:30 UTC | GET | pass | 402 | 210 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 15 ms | — |
| 2026-09-19 11:24 UTC | GET | pass | 402 | 92 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 20 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 13 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | 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
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.