api.craigmbrown.com/v1/services/security.audit-attestation
1.Catalog declaration
| Resource URL | https://api.craigmbrown.com/v1/services/security.audit-attestation |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x5e709929a4ab69ec3a8811d03417869059bc4eb9 |
| Declared price (base units) | 500000 |
| 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-03 04:40 UTC | POST | pass | 402 | 164 ms | — |
| 2026-10-02 13:40 UTC | POST | pass | 402 | 276 ms | — |
| 2026-10-01 13:40 UTC | POST | pass | 402 | 399 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 269 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 144 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 169 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 153 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 354 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 157 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 150 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 585 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 57 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 249 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 177 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 197 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 2123 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 1804 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 100 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 128 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 93 ms | — |
| 2026-09-18 13:40 UTC | POST | pass | 402 | 196 ms | — |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 219 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 122 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 280 ms | — |
| 2026-09-03 17:40 UTC | POST | pass | 402 | 436 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 144 ms | — |
| 2026-09-02 17:40 UTC | POST | pass | 402 | 222 ms | — |
| 2026-09-02 05:40 UTC | POST | pass | 402 | 81 ms | — |
| 2026-09-01 23:40 UTC | POST | pass | 402 | 37 ms | — |
| 2026-08-25 10:47 UTC | POST | pass | 402 | 232 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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 (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 | On-chain tx | Latency |
|---|---|---|---|---|
| 09-02 01:022026-09-02 01:02 UTC | settled (amount + payee) | 200 | 0xe75694b3…97b9 | 1222 ms |
| 500000 units (≈ $0.50 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-25 12:532026-08-25 12:53 UTC | settled (amount + payee) | 200 | 0x46396d7f…bca0 | 1053 ms |
| 500000 units (≈ $0.50 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/a02c3608-7296-4fe6-ac12-a05883908115)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-16 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-04 | 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.