shipapis
StarSubmit an APISubmit API

Lexigram vs Open Food Facts API

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

APILexigramNEW—Open Food Facts APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lexigram vs Open Food Facts API: common questions

Which is more reliable, Lexigram or Open Food Facts API?

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

Open Food Facts API needs no key, while Lexigram requires a free API key. If you want to start calling without signup, reach for Open Food Facts API first.

Can I call Lexigram and Open Food Facts API from the browser?

Only Open Food Facts API 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 Lexigram and Open Food Facts API free for commercial use?

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