api.hergertsynthora.com/v1/ecb-forex-fixing-vs-market
1.Catalog declaration
| Resource URL | https://api.hergertsynthora.com/v1/ecb-forex-fixing-vs-market |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xef879bfd6c4accb8f795136de90246e1ec245e06 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-09 01:03 UTC |
| Catalog-reported calls / payers (30d) | 9 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-09 14:40 UTC | POST | pass | 402 | 587 ms | — |
| 2026-09-08 17:40 UTC | POST | fail | 402 | 591 ms | price_mismatch |
| 2026-09-08 05:40 UTC | POST | fail | 402 | 511 ms | price_mismatch |
| 2026-09-07 17:40 UTC | POST | fail | 402 | 350 ms | price_mismatch |
| 2026-09-07 05:40 UTC | POST | fail | 402 | 396 ms | price_mismatch |
| 2026-09-06 17:40 UTC | POST | fail | 402 | 389 ms | price_mismatch |
| 2026-09-06 05:40 UTC | POST | fail | 402 | 359 ms | price_mismatch |
| 2026-09-05 17:40 UTC | POST | fail | 402 | 433 ms | price_mismatch |
| 2026-09-05 05:40 UTC | POST | fail | 402 | 330 ms | price_mismatch |
| 2026-09-04 17:40 UTC | POST | fail | 402 | 1053 ms | price_mismatch |
| 2026-09-04 05:40 UTC | POST | fail | 402 | 328 ms | price_mismatch |
| 2026-09-03 17:40 UTC | POST | pass | 402 | 408 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 566 ms | — |
| 2026-09-02 17:40 UTC | POST | pass | 402 | 609 ms | — |
| 2026-09-02 05:40 UTC | POST | pass | 402 | 378 ms | — |
| 2026-09-01 23:40 UTC | POST | pass | 402 | 640 ms | — |
| 2026-08-14 08:53 UTC | POST | pass | 402 | 104 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 3 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 |
|---|---|---|---|---|
| 08-28 12:202026-08-28 12:20 UTC | settled (amount + payee) | 200 | 0xcaace120…e264 | 1414 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declaration | ||||
| 08-21 08:332026-08-21 08:33 UTC | settled (amount + payee) | 200 | 0x90457317…e2ec | 1880 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declaration | ||||
| 08-14 10:102026-08-14 10:10 UTC | settled (amount + payee) | 200 | 0x7734a673…e83b | 3478 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declaration | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/5c8108c4-dd49-45b6-bb6d-d3976f3caafd)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.