agent402.tools/v1/images/generations
1.Catalog declaration
| Resource URL | https://agent402.tools/v1/images/generations |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0 |
| Declared price (base units) | 80000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 58 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 16:40 UTC | POST | pass | 402 | 229 ms | — |
| 2026-09-28 22:40 UTC | POST | fail | — | 10006 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 91 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 427 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 261 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 129 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 465 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 1956 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 191 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 107 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 242 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 146 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 214 ms | — |
| 2026-09-17 16:19 UTC | POST | pass | 402 | 139 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 90 ms | — |
| 2026-09-11 11:24 UTC | POST | pass | 402 | 92 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 177 ms | — |
| 2026-09-02 11:24 UTC | POST | pass | 402 | 96 ms | — |
| 2026-08-14 08:53 UTC | POST | fail | 402 | 126 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was 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 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-21 00:002026-09-21 00:00 UTC | settled (nonce-bound) | 200 | 0xfcb114d4…f038 | 6870 ms |
| 80000 units (≈ $0.08 USDC) · L2 not_checked (recorded mismatch)Whose 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/5bd7dcbe-3f1c-47d1-8918-a2667624cee1)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.