shipapis
StarSubmit an APISubmit API

LAPIS vs Open Food Facts API

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

APILAPISNEW—Open Food Facts APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseOpen sequence data (GenBank/Nextstrain-derived); UnverifiedUnverified
Free tierFree — no key (open instance)Free — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LAPIS vs Open Food Facts API: common questions

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

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

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

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

Yes — both LAPIS and Open Food Facts API 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 LAPIS and Open Food Facts API free for commercial use?

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