Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-26 · 4 days ago
agent402.tools/api/http-check
1.Catalog declaration
| Resource URL | https://agent402.tools/api/http-check |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
2026-08-172026-09-26
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-26 10:30 UTC | POST | pass | 402 | 509 ms | — |
| 2026-09-21 11:24 UTC | POST | fail | 402 | 142 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-17 16:19 UTC | POST | fail | 402 | 218 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-15 11:24 UTC | POST | fail | 402 | 84 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-11 11:24 UTC | POST | fail | 402 | 96 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 135 ms | — |
| 2026-09-02 11:25 UTC | POST | pass | 402 | 90 ms | — |
| 2026-08-17 10:39 UTC | POST | fail | 402 | 86 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
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.