shipapis
StarSubmit an APISubmit API

0x vs CryptAPI

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

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

0x vs CryptAPI: common questions

Which is more reliable, 0x or CryptAPI?

On our scheduled checks, CryptAPI leads on measured uptime — 0x 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 0x and CryptAPI need an API key?

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

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

0x 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.