shipapis
StarSubmit an APISubmit API

CryptAPI vs Mempool

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

APICryptAPIHEALTHY94MempoolHEALTHY89
Uptime · 30d
Uptime · 90d100%86.3%
Uptime · 30d100%90.0%
P50 · ms496100
P95 · ms11032258
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseUnverifiedUnverified (open-source project)
Free tierFree API; provider takes ~1% fee per forwarded paymentFree 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

CryptAPI vs Mempool: common questions

Which is more reliable, CryptAPI or Mempool?

On our scheduled checks, CryptAPI leads on measured uptime — CryptAPI 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, CryptAPI or Mempool?

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

Neither needs a paid key — CryptAPI 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 CryptAPI and Mempool from the browser?

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

CryptAPI allows commercial use on its free tier, 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.