Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-13 · today
api.locus.report/api/locus-environmental-context
1.Catalog declaration
| Resource URL | https://api.locus.report/api/locus-environmental-context |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xf121fbecec43e1b616d47285851c20d5fc64431b |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-13 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-08-242026-10-13
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-13 10:30 UTC | POST | pass | 402 | 1440 ms | — |
| 2026-09-27 10:30 UTC | POST | pass | 402 | 1317 ms | — |
| 2026-09-22 11:25 UTC | POST | pass | 402 | 1809 ms | — |
| 2026-09-19 11:24 UTC | POST | pass | 402 | 1020 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 1451 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 773 ms | — |
| 2026-09-09 11:24 UTC | POST | pass | 402 | 1833 ms | — |
| 2026-08-24 11:11 UTC | POST | fail | 400 | 32 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-03 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-03 | 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.