Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-25 · 4 days ago
api.stocktrends.com/v1/leadership/rotation/history
1.Catalog declaration
| Resource URL | https://api.stocktrends.com/v1/leadership/rotation/history |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xaeeb8eabdc05532a26123045f99d208eb1cc00ab |
| Declared price (base units) | 300000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 24 / 1 |
2.Probe history
2026-08-142026-09-25
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-25 10:31 UTC | GET | pass | 402 | 404 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 288 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 210 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 172 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 368 ms | — |
| 2026-09-02 11:24 UTC | GET | fail | 402 | 104 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 258 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-09-14 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-13 | 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.