shipapis
StarSubmit an APISubmit API

bitpay API vs Exchangerate.dev

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

APIbitpay APINEW—Exchangerate.devNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublished12 req/window · 11 remaining · resets 1783515720
In directory since2026-07-052026-07-05
operationalpartialdownno data

bitpay API vs Exchangerate.dev: common questions

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

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

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

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

Only bitpay API is browser-friendly — it returns CORS headers over HTTPS. Exchangerate.dev needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are bitpay API and Exchangerate.dev free for commercial use?

bitpay API has unclear commercial terms, and Exchangerate.dev 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.