Mempool vs OKEx

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

Uptime · 30d
Uptime · 90d86.3%85.3%
Uptime · 30d90.0%96.7%
P50 · ms100192
P95 · ms2258490
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source project)Unverified
Free tierFree public API; no key for basic usageFree tier — API key required
Rate limitEnforced — HTTP 429 on excess, repeated abuse may be banned; numeric limits unpublishedRetry-After: 0s
In directory since2026-07-052026-07-05
operationalpartialdownno data

Mempool vs OKEx: common questions

Which is more reliable, Mempool or OKEx?

On our scheduled checks, Mempool leads on measured uptime — Mempool at 86.3% versus OKEx at 85.3% 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, Mempool or OKEx?

Mempool has the lower median latency in our checks — Mempool responds in 100 ms versus OKEx at 192 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 Mempool and OKEx need an API key?

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

Can I call Mempool and OKEx from the browser?

Yes — both Mempool and OKEx 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 Mempool and OKEx free for commercial use?

Mempool has unclear commercial terms, and OKEx 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.