stable-travel-git-migrate-stabletravel-router-140-merit-systems.vercel.app/api/flightaware/airports/KJFK/weather/observations
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
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 |
| Catalog network | eip155:8453 |
| Receiving address | 0xdd257723b86b4947483905cdacbbbc70facf2ec0 |
| Declared price (base units) | 4000 |
| Catalog status | delisted (since 2026-10-26 13:05 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-22 01:01 UTC |
| Catalog-reported calls / payers (30d) | 8 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-25 18:40 UTC | GET | fail | 410 | 208 ms | no_402HTTP 410 instead of 402 to an unpaid GET. |
| 2026-10-23 16:40 UTC | GET | fail | 410 | 106 ms | no_402HTTP 410 instead of 402 to an unpaid GET. |
| 2026-10-21 22:40 UTC | GET | fail | 410 | 214 ms | no_402HTTP 410 instead of 402 to an unpaid GET. |
| 2026-10-20 16:40 UTC | GET | pass | 402 | 283 ms | — |
| 2026-10-18 22:40 UTC | GET | pass | 402 | 252 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 202 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 185 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 223 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 71 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 120 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 198 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 234 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 185 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 357 ms | — |
| 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 | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 vet402's index”). A settled row reads as nonce-bound when the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 match (no required keys)- the declaration vet402 used marks no key as required, so vet402 checked that the response parsed as a JSON object or array, not which keys it carries.
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 10-02 21:322026-10-02 21:32 UTC | settled (nonce-bound) | 200 | 0x744bccd7…b985 | Base | 1519 ms |
| 4000 units (≈ $0.004 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered | |||||
| 09-25 18:022026-09-25 18:02 UTC | settled (nonce-bound) | 200 | 0x18806941…c8db | Base | 1564 ms |
| 4000 units (≈ $0.004 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered | |||||
| 09-19 12:072026-09-19 12:07 UTC | settled (nonce-bound) | 200 | 0xfce3a0e9…48d0 | Base | 1459 ms |
| 4000 units (≈ $0.004 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered | |||||
Add this badge to your docs
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/35b87484-2628-4a05-8d46-f093613b9501)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-26 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-03 | 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.