agent402.tools/api/skill/security-audit
1.Catalog declaration
| Resource URL | https://agent402.tools/api/skill/security-audit |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0 |
| Declared price (base units) | 17000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | POST | pass | 402 | 1860 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 138 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 319 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 153 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 93 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 247 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 125 ms | — |
| 2026-10-10 03:40 UTC | POST | pass | 402 | 438 ms | — |
| 2026-10-08 22:40 UTC | POST | pass | 402 | 493 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 301 ms | — |
| 2026-10-06 22:40 UTC | POST | pass | 402 | 311 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 169 ms | — |
| 2026-10-04 16:40 UTC | POST | pass | 402 | 235 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 399 ms | — |
| 2026-10-02 22:40 UTC | POST | pass | 402 | 130 ms | — |
| 2026-10-02 04:40 UTC | POST | pass | 402 | 409 ms | — |
| 2026-10-01 13:40 UTC | POST | pass | 402 | 232 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 119 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 374 ms | — |
| 2026-09-28 22:40 UTC | POST | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 208 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 174 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 136 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 268 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 304 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 1228 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 225 ms | — |
| 2026-09-21 11:24 UTC | POST | fail | 402 | 90 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-17 16:19 UTC | POST | fail | 402 | 114 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-15 11:24 UTC | POST | fail | 402 | 95 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
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-24 00:012026-09-24 00:01 UTC | settled (nonce-bound) | 200 | 0x323ba7b8…66e7 | 3077 ms |
| 17000 units (≈ $0.02 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/21dee3e1-c15e-43c5-b8bb-e92af9315c93)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-01 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-24 | 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.