CurrencyFreaks vs GOV.UK Pay API

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

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

CurrencyFreaks vs GOV.UK Pay API: common questions

Which is more reliable, CurrencyFreaks or GOV.UK Pay API?

On our scheduled checks, GOV.UK Pay API leads on measured uptime — CurrencyFreaks 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 CurrencyFreaks and GOV.UK Pay API need an API key?

Both ask you to authenticate — CurrencyFreaks uses an API key and GOV.UK Pay 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 CurrencyFreaks and GOV.UK Pay API from the browser?

Only CurrencyFreaks 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 CurrencyFreaks and GOV.UK Pay API free for commercial use?

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