hotels.use.x402atlas.com/search
1.Catalog declaration
| Resource URL | https://hotels.use.x402atlas.com/search |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x28410eac7393dba041cd5a92eefe7a8e834310bb |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 14 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 22:40 UTC | GET | pass | 402 | 40 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 171 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 284 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 608 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 4 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 11 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 30 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 32 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 37 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 31 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 474 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 127 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 19 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 81 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 27 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 14 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 222 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 12 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 213 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 99 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 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.
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 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-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0xc58e0cff…96fa | 849 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-30 12:072026-08-30 12:07 UTC | settled (amount + payee) | 200 | 0x012efd45…e58e | 710 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-23 12:422026-08-23 12:42 UTC | settled (amount + payee) | 200 | 0x6c446151…73d7 | 875 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-16 12:492026-08-16 12:49 UTC | settled (amount + payee) | 200 | 0xa422de3a…8e80 | 538 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 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/2fd64078-8360-422e-befc-455df9c9ade3)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.