gblin-sentinel.vercel.app/api/data/base-risk-pulse
1.Catalog declaration
| Resource URL | https://gblin-sentinel.vercel.app/api/data/base-risk-pulse |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x0eba5d314f4f5dcb7a094953fa9311a45172dd1b |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 6 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 387 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 274 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 198 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 102 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 510 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 123 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 1898 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 287 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 311 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 213 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 434 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 297 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 2401 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 69 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 278 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 64 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0x0695867d…42de | 3750 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-31 12:082026-08-31 12:08 UTC | settled (amount + payee) | 200 | 0x2e32ab96…9c52 | 3912 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-24 23:342026-08-24 23:34 UTC | settled (amount + payee) | 200 | 0xd4c8d84a…6a5b | 3956 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose 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/e021ddbe-90c1-4b5c-86ef-d79f8b171cff)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.
About the purchase at 2026-08-24T23:34:38Z (UTC). The form starts with that time; add what you saw instead.