liquita-x402-edge.liquita.workers.dev/v1/at-risk
1.Catalog declaration
| Resource URL | https://liquita-x402-edge.liquita.workers.dev/v1/at-risk |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | base |
| Receiving address | 0x6ede3258bce2ef32f9bb614c781818b4efd0e765 |
| Declared price (base units) | — |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 16:40 UTC | GET | pass | 402 | 263 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 473 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 721 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 649 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 650 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 253 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 420 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 747 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 437 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 412 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 827 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 187 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 818 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 14 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 299 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 376 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 2325 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 345 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 251 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 460 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 205 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 179 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 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 |
|---|---|---|---|---|
| 09-11 01:002026-09-11 01:00 UTC | settled (nonce-bound) | 200 | 0x84f106a2…948d | 1854 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-28 12:192026-08-28 12:19 UTC | settled (amount + payee) | 200 | 0x082e8e11…93f2 | 2156 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-21 08:322026-08-21 08:32 UTC | settled (amount + payee) | 200 | 0x5e239e45…32b4 | 1781 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-14 09:572026-08-14 09:57 UTC | settled (amount + payee) | 200 | 0xc6d4552f…f98e | 1896 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose 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/dbabf84e-374d-4bf6-959a-2ce5335e8630)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.