api.recoupable.dev/api/x402/image/generate
1.Catalog declaration
| Resource URL | https://api.recoupable.dev/api/x402/image/generate |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | base |
| Receiving address | 0xbaf31935ed514e8f7da81d0a730ab5362deeeeb7 |
| Declared price (base units) | — |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 804 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 752 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 248 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 157 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 390 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 245 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 213 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 389 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 870 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 348 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 182 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 130 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 284 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 220 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 2020 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 84 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled with a receipt, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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.
2 of those paid attempts are held as inconclusive rather than counted against this seller (2 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 0 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).
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.
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).
settled_4xx- held_reason in the export: the payment settled, then the paid request got a 4xx.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-11 18:022026-09-11 18:02 UTC | settled (nonce-bound) | 400 | 0xa3b2c7fb…f155 | 1180 ms |
| 150000 units (≈ $0.15 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sent | ||||
| 08-29 12:082026-08-29 12:08 UTC | settled (amount + payee) | 400 | 0xaea95487…9bdb | 1065 ms |
| 150000 units (≈ $0.15 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sent | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 0 delivered · 2 inconclusive 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/71c9a4e6-65ac-4b3b-9b44-c4d445615d79)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.
About the purchase at 2026-09-11T18:02:03Z (UTC). The form starts with that time; add what you saw instead.