api.dripmetrics.ai/metrics/amihud-illiquidity
1.Catalog declaration
| Resource URL | https://api.dripmetrics.ai/metrics/amihud-illiquidity |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc9b70d8d342609437bc87ec3c877911a306d3e6a |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-21 01:57 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-16 12:40 UTC | GET | pass | 402 | 1369 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 893 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 1038 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 944 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 2652 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 651 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 958 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 1383 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 896 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 724 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 878 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 733 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 883 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 766 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 473 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 760 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 1034 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 675 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 721 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 710 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 640 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 796 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 271 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 955 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 659 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 1442 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 721 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 1574 ms | — |
| 2026-09-07 23:40 UTC | GET | pass | 402 | 688 ms | — |
| 2026-09-07 14:40 UTC | GET | pass | 402 | 1259 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 match- the response had the 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-06 01:012026-09-06 01:01 UTC | settled (nonce-bound) | 200 | 0xd6f02d01…7af7 | 1721 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose 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/64aa58e4-bf12-4c2a-9279-7370ce6c49fe)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-22 | 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.