hotels.use.x402atlas.com/property
1.Catalog declaration
| Resource URL | https://hotels.use.x402atlas.com/property |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x28410eac7393dba041cd5a92eefe7a8e834310bb |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 13:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 16 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 169 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 288 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 491 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 7 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 11 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 26 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 25 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 17 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 510 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 136 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 18 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 132 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 24 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 33 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 240 ms | — |
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 (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 mismatch- the response lacked 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 |
|---|---|---|---|---|
| 08-24 23:402026-08-24 23:40 UTC | settled (amount + payee) | 200 | 0x743e7a62…a1d6 | 1778 ms |
| 20000 units (≈ $0.02 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-16 12:492026-08-16 12:49 UTC | settled (amount + payee) | 200 | 0xf63f3fba…da78 | 1846 ms |
| 20000 units (≈ $0.02 USDC) · L2 mismatchWhose 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/76825e80-53f0-4dc6-97a3-ee4634a3a051)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.