shipapis
StarSubmit an APISubmit API

bitpay API vs Helium

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

APIbitpay APINEW—HeliumNEW—
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 productionFirst 50 queries per IP free, no key (paid API key beyond, ~$0.02/query)
Rate limitUnpublished50 free queries per IP subnet
In directory since2026-07-052026-07-05
operationalpartialdownno data

bitpay API vs Helium: common questions

Which is more reliable, bitpay API or Helium?

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

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

Can I call bitpay API and Helium from the browser?

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

Are bitpay API and Helium free for commercial use?

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