shipapis
StarSubmit an APISubmit API

0x vs Mempool

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

API0xHEALTHY91MempoolHEALTHY89
Uptime · 30d
Uptime · 90d100%86.3%
Uptime · 30d100%90.0%
P50 · ms622100
P95 · ms34212258
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source project)
Free tierFree — limits not publishedFree public API; no key for basic usage
Rate limitUnpublishedEnforced — HTTP 429 on excess, repeated abuse may be banned; numeric limits unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

0x vs Mempool: common questions

Which is more reliable, 0x or Mempool?

On our scheduled checks, 0x leads on measured uptime — 0x at 100% versus Mempool at 86.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, 0x or Mempool?

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

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

Can I call 0x and Mempool from the browser?

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

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