Currents vs Fixer API

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms586448
P95 · ms1165830
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs Fixer API: common questions

Which is more reliable, Currents or Fixer API?

On our scheduled checks, Currents leads on measured uptime — Currents at 100% versus Fixer API at 99.02% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Currents or Fixer API?

Fixer API has the lower median latency in our checks — Currents responds in 586 ms versus Fixer API at 448 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Currents and Fixer API need an API key?

Both ask you to authenticate — Currents uses an API key and Fixer API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Currents and Fixer API from the browser?

Neither sends browser-friendly CORS headers reliably, so call Currents and Fixer API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Currents and Fixer API free for commercial use?

Currents has unclear commercial terms, and Fixer API 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.