www.amnt.io/api/agent/amnt/logo-generator-gpt15
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://www.amnt.io/api/agent/amnt/logo-generator-gpt15 |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x98fa9c8afb5c56ad27d24843cabebdd55170dbc0 |
| Declared price (base units) | 20000 |
| Catalog status | delisted (since 2026-10-26 01:31 UTC) |
| First seen / last seen | 2026-09-07 01:03 UTC / 2026-10-09 01:02 UTC |
| Catalog-reported calls / payers (30d) | 16 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-25 15:40 UTC | POST | pass | 402 | 605 ms | — |
| 2026-10-23 13:40 UTC | POST | pass | 402 | 634 ms | — |
| 2026-10-21 22:40 UTC | POST | pass | 402 | 682 ms | — |
| 2026-10-20 13:40 UTC | POST | pass | 402 | 875 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 2324 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 595 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 532 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 582 ms | — |
| 2026-10-13 03:40 UTC | POST | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 429 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 417 ms | — |
| 2026-10-10 03:40 UTC | POST | pass | 402 | 446 ms | — |
| 2026-10-08 22:40 UTC | POST | fail | 403 | 123 ms | no_402HTTP 403 instead of 402 to an unpaid POST. |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 293 ms | — |
| 2026-10-06 22:40 UTC | POST | pass | 402 | 751 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 300 ms | — |
| 2026-10-04 16:40 UTC | POST | pass | 402 | 436 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 2309 ms | — |
| 2026-10-02 22:40 UTC | POST | pass | 402 | 2411 ms | — |
| 2026-10-02 04:40 UTC | POST | pass | 402 | 2118 ms | — |
| 2026-09-30 10:30 UTC | POST | pass | 402 | 1001 ms | — |
| 2026-09-25 10:30 UTC | POST | pass | 402 | 470 ms | — |
| 2026-09-17 11:24 UTC | POST | fail | 500 | 1004 ms | no_402HTTP 500 instead of 402 to an unpaid POST. |
| 2026-09-13 11:24 UTC | POST | pass | 402 | 437 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 561 ms | — |
3.L1 — real purchases
1 of 2 paid attempts settled on-chain, and 1 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
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.
L2 match (no required keys)- the declaration vet402 used marks no key as required, so vet402 checked that the response parsed as a JSON object or array, not which keys it carries.
Stage signed- vet402 signed a paid request. vet402 has not settled it on chain yet, or settlement failed, or the seller returned goods without a receipt.
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 10-10 12:022026-10-10 12:02 UTC | settle_failed (withdrawn from the catalog) | 500 | — | Base | 13420 ms |
| 20000 units (≈ $0.02 USDC) · L2 not_checkedWhose side: not sorted: one failure so farLeft out of the public L0 fail count.Stage: signed | |||||
| 10-03 00:012026-10-03 00:01 UTC | settled (nonce-bound) | 200 | 0xa68f05b2…ad77 | Base | 16627 ms |
| 20000 units (≈ $0.02 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/2 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/4955f49c-61cc-4eb5-98b6-781f4fa2ef26)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-26 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-25 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-18 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-13 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-10 | 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.