finance-api.kdlcfa.workers.dev/eth-price
1.Catalog declaration
| Resource URL | https://finance-api.kdlcfa.workers.dev/eth-price |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xe3738580ede5384bb8b8d1c8786b391c59d2668d |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-18 01:06 UTC / 2026-09-08 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-02 23:40 UTC | GET | pass | 402 | 701 ms | — |
| 2026-09-02 14:40 UTC | GET | pass | 402 | 740 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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.
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-02 19:012026-09-02 19:01 UTC | settled (amount + payee) | 200 | 0xf51f3ef3…b187 | 2140 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declaration | ||||
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/86db753c-ffd3-4b7f-89d9-1cf9c5e42067)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-08 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-03 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-02 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-19 | 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.