api.dripmetrics.ai/metrics/cvd
1.Catalog declaration
| Resource URL | https://api.dripmetrics.ai/metrics/cvd |
| 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-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 13 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 16:40 UTC | GET | pass | 402 | 1026 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 761 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 453 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 3115 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 633 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 1095 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 977 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 837 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 1019 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 298 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 614 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 1206 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 938 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 697 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 630 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 522 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 510 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 588 ms | — |
| 2026-08-20 10:50 UTC | GET | fail | 402 | 736 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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-29 15:322026-09-29 15:32 UTC | settled (nonce-bound) | 200 | 0x9ddde121…2e0d | 2759 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-22 00:002026-09-22 00:00 UTC | settled (nonce-bound) | 200 | 0x067449cb…fdcf | 1707 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 2/2 settled · 2 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/e6e74453-f50e-4d2f-b52b-78f4ab23b67c)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.