Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-04 · 1 day ago
ot-intel-api.onrender.com/ot/actor/sector
1.Catalog declaration
| Resource URL | https://ot-intel-api.onrender.com/ot/actor/sector |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x1888192fac6a69e4cd7d078ec4bcf6f24f7c767b |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
2026-08-242026-10-04
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 13:40 UTC | GET | pass | 402 | 2187 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 345 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 361 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-09-29 10:31 UTC | GET | pass | 402 | 352 ms | — |
| 2026-09-24 10:30 UTC | GET | pass | 402 | 420 ms | — |
| 2026-09-20 11:24 UTC | GET | pass | 402 | 233 ms | — |
| 2026-09-17 11:24 UTC | GET | pass | 402 | 293 ms | — |
| 2026-09-13 11:24 UTC | GET | pass | 402 | 305 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 126 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 314 ms | — |
| 2026-08-24 11:11 UTC | GET | fail | 402 | 116 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was 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-09-10 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-07 | 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.