cnvrt.ing/api/analyze-image
1.Catalog declaration
| Resource URL | https://cnvrt.ing/api/analyze-image |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | base |
| Receiving address | 0xfad67ce5a834e68d5533ba7ac08619ff82a42084 |
| Declared price (base units) | — |
| Catalog status | delisted (since 2026-09-30 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 16:40 UTC | POST | unverified | — | 710 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 619 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 843 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 231 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 575 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 289 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 152 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 163 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 467 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 246 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 182 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 195 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 134 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 231 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 86 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 198 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 242 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 234 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 216 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 201 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 141 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 128 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 240 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 2140 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 104 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 150 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 225 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 218 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 199 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 267 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 0 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.
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).
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-16 00:002026-09-16 00:00 UTC | settled (nonce-bound) | 500 | 0x0671fa23…b4ff | 1131 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 09-01 12:092026-09-01 12:09 UTC | settled (amount + payee) | 500 | 0xb0268488…ae57 | 883 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 08-25 12:532026-08-25 12:53 UTC | settled (amount + payee) | 500 | 0xfe8c7c20…50b0 | 981 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 08-19 12:122026-08-19 12:12 UTC | settled (amount + payee) | 500 | 0x898d83c2…99eb | 1412 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 0 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/359afc1f-d606-4431-84e7-430ef0ba10de)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 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.