shipapis
StarSubmit an APISubmit API

BlockCypher vs CryptAPI

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

APIBlockCypherNEW—CryptAPINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree API; provider takes ~1% fee per forwarded payment
Rate limitRetry-After: 1787sUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BlockCypher vs CryptAPI: common questions

Which is more reliable, BlockCypher or CryptAPI?

On our scheduled checks, CryptAPI leads on measured uptime — BlockCypher at —% versus CryptAPI at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do BlockCypher and CryptAPI need an API key?

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

Can I call BlockCypher and CryptAPI from the browser?

Only CryptAPI 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 BlockCypher and CryptAPI free for commercial use?

BlockCypher has unclear commercial terms, and CryptAPI allows commercial use on its free tier. 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.