api.mcx-ventures.com/v2/forensics
1.Catalog declaration
| Resource URL | https://api.mcx-ventures.com/v2/forensics |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x2c9db263f5da45149820e2888e874196fae67fbf |
| Declared price (base units) | 250000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 13:40 UTC | POST | pass | 402 | 484 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 227 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 289 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 270 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 349 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 2343 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 265 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 347 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 231 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 460 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 374 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 530 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 618 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 756 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 102 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 242 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 296 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 164 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 130 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 188 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 375 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 2288 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 576 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 219 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 304 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 2173 ms | — |
| 2026-09-12 22:40 UTC | POST | pass | 402 | 273 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 334 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 222 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 260 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-07 07:012026-09-07 07:01 UTC | settled (nonce-bound) | 200 | 0x1be4a543…0b5f | 7732 ms |
| 250000 units (≈ $0.25 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/e26683b8-a2fb-4bb0-9a84-85e7406d972e)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.