api-dev.cueframe.ai/v1/media
1.Catalog declaration
| Resource URL | https://api-dev.cueframe.ai/v1/media |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:84532 |
| Receiving address | 0x82134912ccc71610da9350ff59cd279fad494a98 |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-10-20 13:01 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-19 13:02 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 10:31 UTC | GET | pass | 402 | 1103 ms | — |
| 2026-09-28 10:30 UTC | GET | pass | 402 | 824 ms | — |
| 2026-09-23 10:31 UTC | GET | pass | 402 | 867 ms | — |
| 2026-09-19 11:24 UTC | GET | pass | 402 | 840 ms | — |
| 2026-09-17 11:24 UTC | GET | pass | 402 | 821 ms | — |
| 2026-09-13 11:24 UTC | GET | pass | 402 | 913 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 651 ms | — |
| 2026-09-05 11:24 UTC | GET | pass | 402 | 591 ms | — |
| 2026-08-14 08:53 UTC | GET | pass | 402 | 686 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-20 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-02 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-29 | 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.