shipapis
StarSubmit an APISubmit API

ExchangeRate-API (open) vs Exchangerate.dev

Same instrument, two spec sheets — measured, not claimed.

APIExchangeRate-API (open)NEW—Exchangerate.devNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished12 req/window · 11 remaining · resets 1783515720
In directory since2026-07-052026-07-05
operationalpartialdownno data

ExchangeRate-API (open) vs Exchangerate.dev: common questions

Which is more reliable, ExchangeRate-API (open) or Exchangerate.dev?

On our scheduled checks, Exchangerate.dev leads on measured uptime — ExchangeRate-API (open) at —% versus Exchangerate.dev at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do ExchangeRate-API (open) and Exchangerate.dev need an API key?

Neither needs a paid key — ExchangeRate-API (open) is callable with no signup, and Exchangerate.dev is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ExchangeRate-API (open) and Exchangerate.dev from the browser?

Only ExchangeRate-API (open) is browser-friendly — it returns CORS headers over HTTPS. Exchangerate.dev needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are ExchangeRate-API (open) and Exchangerate.dev free for commercial use?

ExchangeRate-API (open) has unclear commercial terms, and Exchangerate.dev has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.