ExchangeRate-API (open) vs GOV.UK Pay API
Same instrument, two spec sheets — measured, not claimed.
ExchangeRate-API (open) vs GOV.UK Pay API: common questions
Which is more reliable, ExchangeRate-API (open) or GOV.UK Pay API?
On our scheduled checks, GOV.UK Pay API leads on measured uptime — ExchangeRate-API (open) at —% versus GOV.UK Pay API 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 GOV.UK Pay API need an API key?
ExchangeRate-API (open) needs no key, while GOV.UK Pay API requires a free API key. If you want to start calling without signup, reach for ExchangeRate-API (open) first.
Can I call ExchangeRate-API (open) and GOV.UK Pay API from the browser?
Only ExchangeRate-API (open) is browser-friendly — it returns CORS headers over HTTPS. GOV.UK Pay API needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are ExchangeRate-API (open) and GOV.UK Pay API free for commercial use?
ExchangeRate-API (open) has unclear commercial terms, and GOV.UK Pay 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.