CryptoLabel API vs Mempool

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

Uptime · 30d
Uptime · 90d99.02%86.3%
Uptime · 30d98.3%90.0%
P50 · ms1384100
P95 · ms36982258
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

CryptoLabel API vs Mempool: common questions

Which is more reliable, CryptoLabel API or Mempool?

On our scheduled checks, CryptoLabel API leads on measured uptime — CryptoLabel API at 99.02% 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, CryptoLabel API or Mempool?

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

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

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

CryptoLabel API 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.