coil.trade/api/crypto/setup
1.Catalog declaration
| Resource URL | https://coil.trade/api/crypto/setup |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x7b53524d5c5d29efb8c1d128c56f62fe38cd9476 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-20 01:30 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 704 ms | — |
| 2026-10-18 16:40 UTC | GET | pass | 402 | 500 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 189 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 271 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 316 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 950 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 488 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 573 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 417 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 724 ms | — |
| 2026-10-04 10:30 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-27 10:30 UTC | GET | pass | 402 | 171 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 349 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 297 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 419 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 158 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 20 ms | — |
| 2026-09-04 11:24 UTC | GET | pass | 402 | 37 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 |
|---|---|---|---|---|
| 10-10 08:312026-10-10 08:31 UTC | settled (nonce-bound) | 200 | 0x95b654f9…273d | 1869 ms |
| 50000 units (≈ $0.05 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/a80b58d5-9f51-4294-af96-ecf5f957023b)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-11 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-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
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.