Exchangerate.host vs IBANforge

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not published200 requests/month with a free API key; /v1/demo and /health are keyless
Rate limitUnpublishedUnpublished (200/month free quota)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Exchangerate.host vs IBANforge: common questions

Which is more reliable, Exchangerate.host or IBANforge?

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

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

Can I call Exchangerate.host and IBANforge from the browser?

Yes — both Exchangerate.host and IBANforge send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Exchangerate.host and IBANforge free for commercial use?

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