shipapis
StarSubmit an APISubmit API

Open Food Facts API vs LAPIS

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

APIOpen Food Facts APIUNMONITORED—LAPISNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedOpen sequence data (GenBank/Nextstrain-derived); Unverified
Free tierFree — limits not publishedFree — no key (open instance)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open Food Facts API vs LAPIS: common questions

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

Only LAPIS is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Open Food Facts API and LAPIS need an API key?

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

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

Yes — both Open Food Facts API and LAPIS send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Open Food Facts API and LAPIS free for commercial use?

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