srv1334799.hstgr.cloud/v1/x402/demand/snapshot
1.Catalog declaration
| Resource URL | https://srv1334799.hstgr.cloud/v1/x402/demand/snapshot |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc4f9f3b2cc0eac2542df9f1cb8f5c118e13a0045 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-17 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-16 21:40 UTC | GET | pass | 402 | 168 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 424 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 360 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 282 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 130 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 68 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 187 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 351 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 240 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 464 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 278 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 338 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 284 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 2103 ms | — |
3.L1 — real purchases
3 of 3 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.
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 no_declaration- the listing declares no output schema to check the response against.
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-16 12:092026-09-16 12:09 UTC | settled (nonce-bound) | 200 | 0xe2826657…77d0 | 3503 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-10 01:012026-09-10 01:01 UTC | settled (nonce-bound) | 200 | 0x15f930c7…c1e9 | 3688 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-02 07:022026-09-02 07:02 UTC | settled (amount + payee) | 200 | 0x36718f5f…6ae6 | 3522 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (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/505a66d1-0a10-4872-847e-3bbbbcedd6e2)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-26 | settle_drop | {"calls30d":111} | {"calls30d":8} |
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.