agent402.tools/api/image-gen
1.Catalog declaration
| Resource URL | https://agent402.tools/api/image-gen |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0 |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 10 / 7 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 118 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 265 ms | — |
| 2026-10-17 04:40 UTC | POST | pass | 402 | 99 ms | — |
| 2026-10-15 15:40 UTC | POST | pass | 402 | 125 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 231 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 190 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 486 ms | — |
| 2026-10-10 21:40 UTC | POST | pass | 402 | 147 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 217 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 197 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 102 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 114 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 146 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 432 ms | — |
| 2026-10-02 22:40 UTC | POST | pass | 402 | 543 ms | — |
| 2026-10-01 22:40 UTC | POST | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 308 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 184 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 290 ms | — |
| 2026-09-28 22:40 UTC | POST | fail | — | 10020 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 114 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 2264 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 107 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 93 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 338 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 104 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 276 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 240 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 293 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 |
|---|---|---|---|---|
| 10-03 15:322026-10-03 15:32 UTC | settled (nonce-bound) | 200 | 0x8bfd07f2…39f7 | 11222 ms |
| 30000 units (≈ $0.03 USDC) · L2 not_checkedWhose side: no failure (delivered) | ||||
| 09-27 12:022026-09-27 12:02 UTC | settled (nonce-bound) | 200 | 0x8cc4cd0a…2c46 | 12378 ms |
| 30000 units (≈ $0.03 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered) | ||||
| 09-21 00:012026-09-21 00:01 UTC | settled (nonce-bound) | 200 | 0x0e498026…11a7 | 12920 ms |
| 30000 units (≈ $0.03 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 3/3 settled · 3 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/e1cca1a3-cb1b-45db-974b-d2f155e81ae4)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.