stabletravel.dev/api/flightaware/airports/KMIA/weather/observations
1.Catalog declaration
| Resource URL | https://stabletravel.dev/api/flightaware/airports/KMIA/weather/observations |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xdd257723b86b4947483905cdacbbbc70facf2ec0 |
| Declared price (base units) | 4000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 372 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 282 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 268 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 371 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 92 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 186 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 247 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 52 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 78 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 102 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 124 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 2080 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 49 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 220 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 208 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 335 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 2067 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 157 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 602 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 232 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 266 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled with a receipt, and 2 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-12 00:012026-09-12 00:01 UTC | settled (nonce-bound) | 200 | 0x7f4e8ddf…0711 | 1635 ms |
| 4000 units (≈ $0.004 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-02 12:082026-09-02 12:08 UTC | settled (amount + payee) | 200 | 0xe418d8bb…0224 | 1435 ms |
| 4000 units (≈ $0.004 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/cbd77591-209a-4f0e-b80f-21d7ef422012)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.
About the purchase at 2026-09-12T00:01:32Z (UTC). The form starts with that time; add what you saw instead.