Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago
api.reloadpi.com/api/catalog/topups/offers
1.Catalog declaration
| Resource URL | https://api.reloadpi.com/api/catalog/topups/offers |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x8a598a28a435fe44d31854251b1c88d0781ea822 |
| Declared price (base units) | 2000 |
| 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-252026-10-19
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 278 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 422 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-10-01 10:31 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-26 10:30 UTC | GET | pass | 402 | 371 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 300 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 317 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 299 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 291 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 121 ms | — |
| 2026-08-25 10:47 UTC | GET | fail | 402 | 156 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.