Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-08-16 · 44 days ago
sqlguard.io/v1/probe
1.Catalog declaration
| Resource URL | https://sqlguard.io/v1/probe |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xc8d524703f1751b565a220087d1d4c44a413c1d7 |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-08-28 01:12 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-08-27 01:15 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-08-16
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-08-16 10:39 UTC | POST | fail | 400 | 163 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-08-28 | 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.