data.rcqsignals.com/v1/fetch/macro-event-risk
1.Catalog declaration
| Resource URL | https://data.rcqsignals.com/v1/fetch/macro-event-risk |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x510d1c21788166b0a39f83796bf624e006849690 |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-24 02:00 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 431 ms | — |
| 2026-10-17 22:40 UTC | GET | pass | 402 | 309 ms | — |
| 2026-10-16 15:40 UTC | GET | pass | 402 | 588 ms | — |
| 2026-10-15 03:40 UTC | GET | pass | 402 | 304 ms | — |
| 2026-10-13 21:40 UTC | GET | pass | 402 | 720 ms | — |
| 2026-10-12 15:40 UTC | GET | pass | 402 | 623 ms | — |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 445 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 630 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 552 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 187 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 747 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 146 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 306 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 2346 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 121 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 323 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 333 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 247 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 190 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 427 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 349 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 435 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 224 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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.
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-07 01:002026-09-07 01:00 UTC | settled (nonce-bound) | 200 | 0x329f643e…0be7 | 1448 ms |
| 30000 units (≈ $0.03 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/47514219-b61b-4d7d-ad9b-ddcd2c2d3b72)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-07 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-23 | delisted | {"status":"active"} | {"status":"delisted"} |
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.