shipapis
StarSubmit an APISubmit API

bitpay API vs Exchangerate.host

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

APIbitpay APINEW—Exchangerate.hostNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

bitpay API vs Exchangerate.host: common questions

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

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

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

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

Yes — both bitpay API and Exchangerate.host 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 bitpay API and Exchangerate.host free for commercial use?

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