CryptAPI vs Pharos API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseUnverifiedUnverified
Free tierFree API; provider takes ~1% fee per forwarded paymentFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CryptAPI vs Pharos API: common questions

Which is more reliable, CryptAPI or Pharos API?

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

CryptAPI needs no key, while Pharos API requires a free API key. If you want to start calling without signup, reach for CryptAPI first.

Can I call CryptAPI and Pharos API from the browser?

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

Are CryptAPI and Pharos API free for commercial use?

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