cryptyx.ai/api/market-pulse/regime
1.Catalog declaration
| Resource URL | https://cryptyx.ai/api/market-pulse/regime |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x0cd2c9724f185a029101b4aeacf3f114415c394f |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 04:40 UTC | GET | pass | 402 | 280 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 169 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 486 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 290 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 585 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 556 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 391 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 381 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 367 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 199 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 208 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 386 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 274 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 182 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 132 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 210 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 2151 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 391 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 754 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 362 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 628 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 369 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 441 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 548 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 621 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 587 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 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-06 19:012026-09-06 19:01 UTC | settled (nonce-bound) | 200 | 0x12fc174c…0f51 | 2416 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose 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/cef47e6c-38ae-426c-b842-cd9a594c1229)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-30 | 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.