Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-04 · 1 day ago
agents.ai-rook.com/api/ip-lookup
1.Catalog declaration
| Resource URL | https://agents.ai-rook.com/api/ip-lookup |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xd5f96558fcb1f127c77c7d95eea067f526d08618 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 39 / 6 |
2.Probe history
2026-09-072026-10-04
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 13:40 UTC | GET | fail | 200 | 302 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-10-03 16:40 UTC | GET | fail | 200 | 450 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-10-02 22:40 UTC | GET | fail | 200 | 290 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-10-01 22:40 UTC | GET | fail | 200 | 293 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-10-01 04:40 UTC | GET | fail | 200 | 325 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-30 13:40 UTC | GET | fail | 200 | 241 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-29 16:40 UTC | GET | fail | 200 | 527 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-28 22:40 UTC | GET | fail | 200 | 156 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-28 04:40 UTC | GET | fail | 200 | 323 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-27 13:40 UTC | GET | fail | 200 | 261 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-26 16:40 UTC | GET | fail | 200 | 305 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-26 04:40 UTC | GET | fail | 200 | 319 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-25 13:40 UTC | GET | fail | 200 | 274 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-24 16:40 UTC | GET | fail | 200 | 157 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-23 22:40 UTC | GET | fail | 200 | 271 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-23 04:40 UTC | GET | fail | 200 | 282 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-22 13:40 UTC | GET | fail | 200 | 354 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-21 16:40 UTC | GET | fail | 200 | 1745 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-20 22:40 UTC | GET | fail | 200 | 330 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-20 04:40 UTC | GET | fail | 200 | 147 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-19 13:40 UTC | GET | fail | 200 | 196 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-18 16:40 UTC | GET | fail | 200 | 109 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-18 04:40 UTC | GET | fail | 200 | 184 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-17 13:40 UTC | GET | fail | 200 | 141 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-16 16:40 UTC | GET | fail | 200 | 106 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-15 22:40 UTC | GET | fail | 200 | 2338 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-15 04:40 UTC | GET | fail | 200 | 91 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-14 16:40 UTC | GET | fail | 200 | 917 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-11 11:24 UTC | GET | fail | 200 | 200 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-07 11:24 UTC | GET | fail | 200 | 243 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
No listing changes observed.
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.