Blockchair vs BlockCypher

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

Uptime · 30d
Uptime · 90d98.0%30.4%
Uptime · 30d98.3%36.7%
P50 · ms729145
P95 · ms13231129
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedRetry-After: 1787s
In directory since2026-07-052026-07-05
operationalpartialdownno data

Blockchair vs BlockCypher: common questions

Which is more reliable, Blockchair or BlockCypher?

On our scheduled checks, Blockchair leads on measured uptime — Blockchair at 98.0% versus BlockCypher at 30.4% 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, Blockchair or BlockCypher?

BlockCypher has the lower median latency in our checks — Blockchair responds in 729 ms versus BlockCypher at 145 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 Blockchair and BlockCypher need an API key?

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

Can I call Blockchair and BlockCypher from the browser?

Only Blockchair is browser-friendly — it returns CORS headers over HTTPS. BlockCypher needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Blockchair and BlockCypher free for commercial use?

Blockchair has unclear commercial terms, and BlockCypher 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.