ExchangeRate-API vs exchangerate.dev
For programmatic currency exchange rates and forex data with intraday freshness, per-value provenance, and MCP-native access, exchangerate.dev is the stronger default. Keep ExchangeRate-API if once-daily rates and ~1,500 calls a month are enough.
exchangerate.dev
Best for buildersA currency API for foreign exchange (forex) rates. Major currency pairs refresh intraday (~60s on trading days) — most others too, every value labelled with its source and market_session, MCP on every plan.
From $0 · free tier, 10,000 calls/mo, no card
Get API keyExchangeRate-API
IncumbentSimple, reliable FX API with a no-card free tier. Rates update once per day.
Free (1,500/mo) → paid
Currency and forex API comparison
| Capability | exchangerate.dev | ExchangeRate-API |
|---|---|---|
| Free-tier limit | 10,000 calls/mo | 1,500 calls/mo |
| Intraday refresh (majors + most pairs) | ✓ ~60s on trading days | ✗ once daily |
| Per-value source + market_session | ✓ Yes | ✗ No |
| MCP server (every plan, incl. free) | ✓ Yes | ✗ No |
| Historical daily series | ✓ to 1999 | ✓ (paid) |
| No credit card to start | ✓ Yes | ✓ Yes |
Where exchangerate.dev wins
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.
Where ExchangeRate-API leads
ExchangeRate-API is dead-simple to start and has a strong uptime reputation. If once-daily rates and ~1,500 calls a month cover you, it is an easy pick. exchangerate.dev gives roughly 6× the free calls, intraday freshness, per-value provenance, and MCP on every plan.
Verdict
Choose exchangerate.dev when intraday freshness, per-value provenance, MCP-native access, and free-tier headroom matter. Keep ExchangeRate-API if once-daily rates and ~1,500 calls a month are enough. Both speak REST JSON over HTTPS; compare the endpoint and response shape before changing an integration.