stable-travel-git-migrate-stabletravel-router-140-merit-systems.vercel.app/api/flightaware/airports/KJFK/weather/observations
1.Catalog declaration
| Resource URL | https://stable-travel-git-migrate-stabletravel-router-140-merit-systems.vercel.app/api/flightaware/airports/KJFK/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-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 22:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 82 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 76 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 227 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 376 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 107 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 2039 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 243 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 610 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 266 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 515 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 117 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 231 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 308 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 182 ms | — |
| 2026-08-24 11:11 UTC | GET | fail | 402 | 70 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
2 of 2 paid attempts settled on-chain, and 2 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.
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-25 18:022026-09-25 18:02 UTC | settled (nonce-bound) | 200 | 0x18806941…c8db | 1564 ms |
| 4000 units (≈ $0.004 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-19 12:072026-09-19 12:07 UTC | settled (nonce-bound) | 200 | 0xfce3a0e9…48d0 | 1459 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/35b87484-2628-4a05-8d46-f093613b9501)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.