Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · today
autopulse.theaslangroupllc.com/api/auto/value
1.Catalog declaration
| Resource URL | https://autopulse.theaslangroupllc.com/api/auto/value |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x50ab2018c06c6e4eaa9ba52057eb55ed284912fc |
| Declared price (base units) | 80000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-19 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-08-262026-10-19
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 10:30 UTC | GET | pass | 402 | 53 ms | — |
| 2026-09-19 11:24 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 48 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 56 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 63 ms | — |
| 2026-08-26 10:33 UTC | GET | fail | 402 | 59 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-16 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-20 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-09 | 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
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.