shipapis
StarSubmit an APISubmit API

Exchange Rates API vs Exchangerate.host

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

APIExchange Rates APINEW—Exchangerate.hostNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Exchange Rates API vs Exchangerate.host: common questions

Which is more reliable, Exchange Rates API or Exchangerate.host?

On our scheduled checks, Exchangerate.host leads on measured uptime — Exchange Rates API at —% versus Exchangerate.host 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 Exchange Rates API and Exchangerate.host need an API key?

Neither needs a paid key — Exchange Rates API is callable with no signup, and Exchangerate.host is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Exchange Rates API and Exchangerate.host from the browser?

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

Are Exchange Rates API and Exchangerate.host free for commercial use?

Exchange Rates API has unclear commercial terms, and Exchangerate.host 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.