Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago
api.healthparse.io/v1/open-payments/recipients/yoy-increase/search
1.Catalog declaration
| Resource URL | https://api.healthparse.io/v1/open-payments/recipients/yoy-increase/search |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x177ea123a35253ba8869a7e21e717978e482351d |
| Declared price (base units) | 100000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-14 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-08-312026-10-19
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-10-17 22:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-10-16 15:40 UTC | GET | pass | 402 | 298 ms | — |
| 2026-10-15 03:40 UTC | GET | pass | 402 | 522 ms | — |
| 2026-10-13 21:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-10-12 15:40 UTC | GET | pass | 402 | 368 ms | — |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 266 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 343 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 519 ms | — |
| 2026-10-04 10:30 UTC | GET | pass | 402 | 270 ms | — |
| 2026-09-27 10:30 UTC | GET | pass | 402 | 352 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 119 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 231 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 61 ms | — |
| 2026-08-31 11:24 UTC | GET | fail | 402 | 76 ms | accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-06 | 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.