api.magentlab.com/api/calc/bars
1.Catalog declaration
| Resource URL | https://api.magentlab.com/api/calc/bars |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x836be278f1739fb4308091cd1852f7971bc19ee2 |
| Declared price (base units) | 5000 |
| Catalog status | delisted (since 2026-10-18 13:04 UTC) |
| First seen / last seen | 2026-09-01 01:03 UTC / 2026-10-17 13:04 UTC |
| Catalog-reported calls / payers (30d) | 5 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 22:40 UTC | POST | pass | 402 | 249 ms | — |
| 2026-10-02 04:40 UTC | POST | pass | 402 | 571 ms | — |
| 2026-10-01 13:40 UTC | POST | pass | 402 | 165 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 372 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 828 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 342 ms | — |
| 2026-09-07 17:40 UTC | POST | fail | — | 10000 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-07 05:40 UTC | POST | fail | — | 10014 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-06 14:40 UTC | POST | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-05 23:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-09-05 14:40 UTC | POST | pass | 402 | 148 ms | — |
| 2026-09-04 23:40 UTC | POST | pass | 402 | 1492 ms | — |
| 2026-09-04 14:40 UTC | POST | pass | 402 | 34 ms | — |
| 2026-09-03 23:40 UTC | POST | pass | 402 | 107 ms | — |
| 2026-09-03 14:40 UTC | POST | pass | 402 | 74 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 333 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-18 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-28 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-08 | 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.