shipapis
StarSubmit an APISubmit API

bitpay API vs Edgrapi

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

APIbitpay APIHEALTHY93EdgrapiHEALTHY79
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms4891662
P95 · ms22443997
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

bitpay API vs Edgrapi: common questions

Which is more reliable, bitpay API or Edgrapi?

On our scheduled checks, bitpay API leads on measured uptime — bitpay API at 100% versus Edgrapi at 99.02% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, bitpay API or Edgrapi?

bitpay API has the lower median latency in our checks — bitpay API responds in 489 ms versus Edgrapi at 1662 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do bitpay API and Edgrapi need an API key?

Both ask you to authenticate — bitpay API uses an API key and Edgrapi 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 bitpay API and Edgrapi from the browser?

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

Are bitpay API and Edgrapi free for commercial use?

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