Mempool vs Nexchange

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

Uptime · 30d
Uptime · 90d86.3%99.02%
Uptime · 30d90.0%98.3%
P50 · ms100281
P95 · ms22583199
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source project)Unverified
Free tierFree public API; no key for basic usageFree — limits not published
Rate limitEnforced — HTTP 429 on excess, repeated abuse may be banned; numeric limits unpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Mempool vs Nexchange: common questions

Which is more reliable, Mempool or Nexchange?

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

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

Neither needs a paid key — Mempool is callable with no signup, and Nexchange is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Mempool and Nexchange from the browser?

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

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