coil.trade/api/crypto/day
1.Catalog declaration
| Resource URL | https://coil.trade/api/crypto/day |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x7b53524d5c5d29efb8c1d128c56f62fe38cd9476 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-20 01:30 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 6 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 16:40 UTC | GET | pass | 402 | 462 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 590 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 624 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 839 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 196 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 396 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 445 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 561 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 346 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 411 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 594 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 657 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 644 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 212 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 515 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 560 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 277 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 620 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 349 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 394 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 553 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 158 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 175 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 2418 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 531 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 515 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 414 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 mismatch- the response lacked fields the listing's output schema declares.
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-17 15:282026-09-17 15:28 UTC | settled (nonce-bound) | 200 | 0x1ebb7285…8c16 | 2314 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-11 12:082026-09-11 12:08 UTC | settled (nonce-bound) | 200 | 0x664e8d36…41b6 | 2208 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-05 01:002026-09-05 01:00 UTC | settled (nonce-bound) | 200 | 0x2397a5ca…60ec | 1790 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/1b31626f-2723-419e-aaf3-3af542c015c5)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.