apiacre.com/v1/data/ecb-fx-reference
1.Catalog declaration
| Resource URL | https://apiacre.com/v1/data/ecb-fx-reference |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xa0bfa4f07281c9b248dc3aed2217836bca24869b |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-20 01:30 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 22:40 UTC | POST | pass | 402 | 2405 ms | — |
| 2026-10-18 13:40 UTC | POST | pass | 402 | 2400 ms | — |
| 2026-10-17 04:40 UTC | POST | pass | 402 | 449 ms | — |
| 2026-10-15 15:40 UTC | POST | pass | 402 | 538 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 460 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 429 ms | — |
| 2026-10-11 21:40 UTC | POST | pass | 402 | 285 ms | — |
| 2026-10-10 21:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-10-09 15:40 UTC | POST | pass | 402 | 2525 ms | — |
| 2026-10-08 13:40 UTC | POST | pass | 402 | 309 ms | — |
| 2026-10-07 13:40 UTC | POST | pass | 402 | 2316 ms | — |
| 2026-10-06 13:40 UTC | POST | pass | 402 | 438 ms | — |
| 2026-10-05 04:40 UTC | POST | pass | 402 | 284 ms | — |
| 2026-10-04 10:30 UTC | POST | pass | 402 | 321 ms | — |
| 2026-09-27 10:30 UTC | POST | pass | 402 | 173 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 325 ms | — |
| 2026-09-18 11:24 UTC | POST | pass | 402 | 396 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 167 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 405 ms | — |
| 2026-09-08 11:24 UTC | POST | pass | 402 | 174 ms | — |
| 2026-09-04 11:24 UTC | POST | pass | 402 | 396 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 |
|---|---|---|---|---|
| 10-12 02:312026-10-12 02:31 UTC | settled (nonce-bound) | 200 | 0x96293b6b…70e6 | 2107 ms |
| 2000 units (≈ $0.002 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/7b0fab9f-4e43-4b6a-a145-b5bcf86ecb3e)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-06 | 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.