Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-04 · 1 day ago
agents.ai-rook.com/api/market-pulse
1.Catalog declaration
| Resource URL | https://agents.ai-rook.com/api/market-pulse |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xd5f96558fcb1f127c77c7d95eea067f526d08618 |
| Declared price (base units) | 25000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 30 / 1 |
2.Probe history
2026-09-132026-10-04
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 16:40 UTC | GET | fail | 200 | 739 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-10-03 22:40 UTC | GET | fail | 200 | 1447 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-10-03 04:40 UTC | GET | fail | 200 | 537 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-10-02 04:40 UTC | GET | fail | 200 | 487 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-10-01 13:40 UTC | GET | fail | 200 | 651 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-30 16:40 UTC | GET | fail | 200 | 876 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-29 22:40 UTC | GET | fail | 200 | 598 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-29 04:40 UTC | GET | fail | 200 | 540 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-28 13:40 UTC | GET | fail | 200 | 569 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-27 16:40 UTC | GET | fail | 200 | 545 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-26 22:40 UTC | GET | fail | 200 | 616 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-26 04:40 UTC | GET | fail | 200 | 608 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-25 13:40 UTC | GET | fail | 200 | 637 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-24 16:40 UTC | GET | fail | 200 | 481 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-23 22:40 UTC | GET | fail | 200 | 519 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-23 04:40 UTC | GET | fail | 200 | 682 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-22 13:40 UTC | GET | fail | 200 | 1184 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-21 16:40 UTC | GET | fail | 200 | 566 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-20 22:40 UTC | GET | fail | 200 | 619 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-20 04:40 UTC | GET | fail | 200 | 839 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-19 13:40 UTC | GET | fail | 200 | 460 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-18 22:40 UTC | GET | fail | 200 | 825 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-18 04:40 UTC | GET | fail | 200 | 661 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-17 13:40 UTC | GET | fail | 200 | 470 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-16 16:40 UTC | GET | fail | 200 | 464 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-15 22:40 UTC | GET | fail | 200 | 513 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-15 04:40 UTC | GET | fail | 200 | 472 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-14 16:40 UTC | GET | fail | 200 | 683 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-13 22:40 UTC | GET | fail | 200 | 814 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-13 13:40 UTC | GET | fail | 200 | 499 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.