nectar-tools.fly.dev/v1/crypto-quote
1.Catalog declaration
| Resource URL | https://nectar-tools.fly.dev/v1/crypto-quote |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x389ba2fab205f20724d9d7014669e172a37f9b42 |
| Declared price (base units) | 15000 |
| Catalog status | delisted (since 2026-09-24 01:02 UTC) |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-23 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-23 13:40 UTC | POST | fail | — | 11 ms | dnsThe host name did not resolve. |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 57 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 94 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 136 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 235 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 92 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 219 ms | — |
| 2026-09-18 13:40 UTC | POST | pass | 402 | 216 ms | — |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 123 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 34 ms | — |
| 2026-09-16 13:40 UTC | POST | pass | 402 | 406 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 34 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 128 ms | — |
| 2026-09-14 04:40 UTC | POST | pass | 402 | 75 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 115 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 63 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 78 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 256 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 2545 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-07 23:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-09-07 14:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-06 17:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-06 05:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-09-05 17:40 UTC | GET | pass | 402 | 2140 ms | — |
| 2026-09-05 05:40 UTC | GET | pass | 402 | 141 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 (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 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 |
|---|---|---|---|---|
| 09-04 01:012026-09-04 01:01 UTC | settled (amount + payee) | 200 | 0x5e3a2d93…d0fa | 1581 ms |
| 15000 units (≈ $0.01 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/85ebcc50-8885-4da8-8d45-b9c06ad7025c)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-24 | 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.