x402-adsb.x402-adsb-worker.workers.dev/aircraft
1.Catalog declaration
| Resource URL | https://x402-adsb.x402-adsb-worker.workers.dev/aircraft |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x751c6acf5d1b704a1ad983a526207600968b4e41 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 8 / 7 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 13:40 UTC | GET | pass | 402 | 268 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 1178 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 261 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 407 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 2304 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 400 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 638 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 458 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 369 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 2067 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 357 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 211 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 373 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 222 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 524 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 627 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 506 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 409 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 351 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 400 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 348 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 642 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 419 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 449 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 556 ms | — |
3.L1 — real purchases
3 of 4 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.
settle_failed- vet402 signed a payment and got no settlement receipt back.
L2 no_declaration- the listing declares no output schema to check the response against.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-23 18:012026-09-23 18:01 UTC | settled (nonce-bound) | 200 | 0x0cf94f80…d033 | 2771 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-17 12:092026-09-17 12:09 UTC | settled (nonce-bound) | 200 | 0x13cd662d…c58e | 3021 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-11 01:012026-09-11 01:01 UTC | settled (nonce-bound) | 200 | 0xa4daa6a2…b27a | 3094 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-03 01:012026-09-03 01:01 UTC | settle_failed | 503 | — | 963 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/4 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/4927a3bd-5d22-477a-adec-fffb768f475f)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.