ICD-10 Codes vs Open Food Facts

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

Uptime · 30d
Uptime · 90d100%39.2%
Uptime · 30d100%33.3%
P50 · ms18311556
P95 · ms38982836
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 Open Food Facts: common questions

Which is more reliable, ICD-10 Codes or Open Food Facts?

On our scheduled checks, ICD-10 Codes leads on measured uptime — ICD-10 Codes at 100% versus Open Food Facts at 39.2% 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, ICD-10 Codes or Open Food Facts?

Open Food Facts has the lower median latency in our checks — ICD-10 Codes responds in 1831 ms versus Open Food Facts at 1556 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 ICD-10 Codes and Open Food Facts need an API key?

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

Can I call ICD-10 Codes and Open Food Facts from the browser?

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

Are ICD-10 Codes and Open Food Facts free for commercial use?

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