api.reloadpi.com/api/catalog/esims/offers
1.Catalog declaration
| Resource URL | https://api.reloadpi.com/api/catalog/esims/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) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 369 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 426 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 489 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 657 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 392 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 369 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 297 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 336 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 238 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 250 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 611 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 134 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 496 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 670 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 594 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 301 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 326 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 570 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 619 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 731 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 335 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 2351 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 328 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 238 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 2107 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 match- the response had the fields the listing's output schema declares.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-17 12:532026-09-17 12:53 UTC | settled (nonce-bound) | 200 | 0x1fce8862…2264 | 1820 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-11 01:012026-09-11 01:01 UTC | settled (nonce-bound) | 200 | 0xb4b99a4c…c8b9 | 1087 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-03 12:082026-09-03 12:08 UTC | settled (amount + payee) | 200 | 0x77094db5…b6fc | 1412 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/64e52c65-416a-4c09-abe3-79663675ce00)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.