Lexigram vs Open Food Facts

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

Uptime · 30d
Uptime · 90d99.02%39.2%
Uptime · 30d98.3%33.3%
P50 · ms8071556
P95 · ms16722836
AuthapiKeynone
CORSnono
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: common questions

Which is more reliable, Lexigram or Open Food Facts?

On our scheduled checks, Lexigram leads on measured uptime — Lexigram at 99.02% 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, Lexigram or Open Food Facts?

Lexigram has the lower median latency in our checks — Lexigram responds in 807 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 Lexigram and Open Food Facts need an API key?

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

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

Neither sends browser-friendly CORS headers reliably, so call Lexigram and Open Food Facts from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Lexigram and Open Food Facts free for commercial use?

Lexigram 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.