aviationstack.mpp.tempo.xyz/v1/airports
1.Catalog declaration
| Resource URL | https://aviationstack.mpp.tempo.xyz/v1/airports |
| Source | mpp_directory |
| Declared method | GET |
| Catalog network | eip155:4217 |
| Receiving address | 0xca4e835f803cb0b7c428222b3a3b98518d4779fe |
| Declared price (base units) | 5000 |
| Catalog status | delisted (since 2026-10-02 01:05 UTC) |
| First seen / last seen | 2026-09-17 12:35 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | — / — |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 22:40 UTC | GET | fail | 404 | 376 ms | no_402HTTP 404 instead of 402 to an unpaid GET. |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 63 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 369 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 465 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 142 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 1674 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 646 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 377 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 399 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 2212 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 479 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 153 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 259 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 252 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 557 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 2087 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 288 ms | — |
| 2026-09-17 12:35 UTC | GET | pass | 402 | 338 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 our 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 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example in the 402 (extensions.bazaar.info.output.example) counts as a declaration. When the catalog also declares an output, the example's top-level keys are required. When it does not, vet402 checks that the response is a JSON object or array, and the record page reads match (no required keys).
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 |
|---|---|---|---|---|---|
| 09-30 12:002026-09-30 12:00 UTC | settled (nonce-bound) | 200 | 0x78cb4de0…285f | Tempo | 2037 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 09-24 06:002026-09-24 06:00 UTC | settled (nonce-bound) | 200 | 0xf8eef0d5…41ce | Tempo | 1094 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 09-17 15:262026-09-17 15:26 UTC | settled (nonce-bound) | 200 | 0x08838904…12f5 | Tempo | 2659 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: 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/b5a583d4-3a9f-491f-b1f5-29b449e91383)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-02 | 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.