Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-21 · 16 days ago
preview.agenticinsights.com/api/x402/agentic-market/validate
1.Catalog declaration
| Resource URL | https://preview.agenticinsights.com/api/x402/agentic-market/validate |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:84532 |
| Receiving address | 0x355e413514dbe87b335b765e1ee5c947db8a941b |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-09-24 01:02 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-23 01:02 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
2026-08-142026-09-21
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-21 11:24 UTC | GET | fail | 403 | 77 ms | no_402HTTP 403 instead of 402 to an unpaid GET. |
| 2026-09-17 16:19 UTC | GET | fail | 403 | 220 ms | no_402HTTP 403 instead of 402 to an unpaid GET. |
| 2026-09-14 11:24 UTC | GET | fail | 403 | 70 ms | no_402HTTP 403 instead of 402 to an unpaid GET. |
| 2026-09-11 11:24 UTC | GET | fail | 403 | 65 ms | no_402HTTP 403 instead of 402 to an unpaid GET. |
| 2026-09-07 11:24 UTC | GET | fail | 403 | 130 ms | no_402HTTP 403 instead of 402 to an unpaid GET. |
| 2026-09-02 11:24 UTC | GET | fail | 403 | 2071 ms | no_402HTTP 403 instead of 402 to an unpaid GET. |
| 2026-08-14 08:53 UTC | GET | fail | 403 | 26 ms | no_402HTTP 403 instead of 402 to an unpaid GET. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-24 | 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.