shelf.thirdmade.net/probe/image-gen
1.Catalog declaration
| Resource URL | https://shelf.thirdmade.net/probe/image-gen |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x315708415764b7f2b783714ce82cf9c628e33fcf |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-31 01:03 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 22:40 UTC | POST | pass | 402 | 854 ms | — |
| 2026-10-17 16:40 UTC | POST | pass | 402 | 741 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 649 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 711 ms | — |
| 2026-10-13 10:31 UTC | POST | pass | 402 | 438 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 247 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 792 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 489 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 260 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 535 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 492 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 383 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 73 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 125 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 90 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 651 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 31 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 147 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 898 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 1074 ms | — |
| 2026-09-18 13:40 UTC | POST | pass | 402 | 510 ms | — |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 793 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 86 ms | — |
| 2026-09-16 13:40 UTC | POST | pass | 402 | 26 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 575 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 582 ms | — |
| 2026-09-14 04:40 UTC | POST | pass | 402 | 530 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 331 ms | — |
| 2026-09-12 22:40 UTC | POST | pass | 402 | 849 ms | — |
| 2026-09-12 13:40 UTC | POST | pass | 402 | 364 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 no_declaration- the listing declares no output schema to check the response against.
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-06 01:022026-09-06 01:02 UTC | settled (nonce-bound) | 200 | 0x5c0dae9d…a10f | 1200 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose 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/bf2a0328-91ac-4a2f-af21-fe486486abd2)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-12 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-30 | 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.