FoodData Central vs Lexigram

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree tier — key may be required
Rate limit10 req/window · 9 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

FoodData Central vs Lexigram: common questions

Which is more reliable, FoodData Central or Lexigram?

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

Both ask you to authenticate — FoodData Central uses an API key and Lexigram uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call FoodData Central and Lexigram from the browser?

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

Are FoodData Central and Lexigram free for commercial use?

FoodData Central has unclear commercial terms, and Lexigram 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.