Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-20 · today
api.agentstools.dev/insider/trades
1.Catalog declaration
| Resource URL | https://api.agentstools.dev/insider/trades |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xf22e558a00d91ee12a1f50c52186fecb8ddff493 |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
2026-08-212026-10-20
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 10:30 UTC | GET | pass | 402 | 410 ms | — |
| 2026-09-30 10:30 UTC | GET | pass | 402 | 468 ms | — |
| 2026-09-25 10:30 UTC | GET | pass | 402 | 580 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 136 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 163 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 146 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 132 ms | — |
| 2026-08-21 10:55 UTC | GET | fail | 402 | 132 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-25 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-17 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-08-18 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-15 | 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.