For programmatic, intraday-fresh FX rates with per-value provenance and MCP-native access, exchangerate.dev is the stronger default. Keep ExchangeRate.host if you make only occasional EOD historical lookups.
If your rates flow into code — payments, dashboards, backtests — exchangerate.dev fits how you already work. Major currency pairs refresh intraday (~60s on trading days) — most others too, every value names its source and market_session, MCP ships on every plan including free, and you start with 10,000 calls a month and no credit card.
ExchangeRate.host is convenient for occasional end-of-day historical lookups. For anything beyond ~100 requests a month — or where intraday freshness, provenance, or MCP matter — exchangerate.dev is the better fit; its free tier alone covers 10,000 calls.
Choose exchangerate.dev when intraday freshness, per-value provenance, MCP-native access, and free-tier headroom matter. Keep ExchangeRate.host if you make only occasional EOD historical lookups. Both speak REST JSON over HTTPS, and exchangerate.dev accepts Frankfurter-compatible parameters — so trying it is low-risk.
Rates are from the free tier, updated intraday on trading days. Indicative only, not for settlement or regulated trading.