ICD-10 Codes vs openFDA API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ICD-10 Codes vs openFDA API: common questions

Which is more reliable, ICD-10 Codes or openFDA API?

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

Neither needs a paid key — ICD-10 Codes is callable with no signup, and openFDA API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ICD-10 Codes and openFDA API from the browser?

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

Are ICD-10 Codes and openFDA API free for commercial use?

ICD-10 Codes has unclear commercial terms, and openFDA 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.