Banking API vs Exchangerate.host

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Banking API vs Exchangerate.host: common questions

Which is more reliable, Banking API or Exchangerate.host?

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

Exchangerate.host needs no key, while Banking API requires a free API key. If you want to start calling without signup, reach for Exchangerate.host first.

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

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

Are Banking API and Exchangerate.host free for commercial use?

Banking 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.