Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-17 · 10 days ago
agentdatum.com/api/v1/d/geopol-risk
1.Catalog declaration
| Resource URL | https://agentdatum.com/api/v1/d/geopol-risk |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xcd265870a20db25250535cb8a0d3bb0850417902 |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-09-17 12:35 UTC) |
| First seen / last seen | 2026-08-16 01:07 UTC / 2026-09-17 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
2026-09-012026-09-17
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-17 04:40 UTC | GET | fail | 410 | 547 ms | no_402 |
| 2026-09-16 13:40 UTC | GET | fail | 410 | 940 ms | no_402 |
| 2026-09-15 16:40 UTC | GET | fail | 200 | 1179 ms | no_402 |
| 2026-09-14 22:40 UTC | GET | unverified | 429 | 892 ms | rate_limited |
| 2026-09-14 11:24 UTC | GET | unverified | 429 | 3920 ms | rate_limited |
| 2026-09-10 11:24 UTC | GET | fail | 200 | 2718 ms | no_402 |
| 2026-09-06 11:24 UTC | GET | fail | 200 | 1039 ms | no_402 |
| 2026-09-01 23:14 UTC | GET | unverified | 429 | 1172 ms | rate_limited |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-17 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-08-18 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-17 | 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.