shipapis
StarSubmit an APISubmit API

Bitmex vs CryptAPI

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

APIBitmexDEAD0CryptAPIHEALTHY94
Uptime · 30d
Uptime · 90d2.9%100%
Uptime · 30d0.0%100%
P50 · ms840496
P95 · ms8401103
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree API; provider takes ~1% fee per forwarded payment
Rate limit300 req/window · 299 remaining · resets 1783520161Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bitmex vs CryptAPI: common questions

Which is more reliable, Bitmex or CryptAPI?

On our scheduled checks, CryptAPI leads on measured uptime — Bitmex at 2.9% versus CryptAPI at 100% 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, Bitmex or CryptAPI?

CryptAPI has the lower median latency in our checks — Bitmex responds in 840 ms versus CryptAPI at 496 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 Bitmex and CryptAPI need an API key?

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

Can I call Bitmex and CryptAPI from the browser?

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

Are Bitmex and CryptAPI free for commercial use?

Bitmex has unclear commercial terms, and CryptAPI allows commercial use on its free tier. 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.