LAPIS vs TheMealDB

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms524198
P95 · ms846696
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 TheMealDB: common questions

Which is more reliable, LAPIS or TheMealDB?

Both are neck-and-neck — LAPIS and TheMealDB each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, LAPIS or TheMealDB?

TheMealDB has the lower median latency in our checks — LAPIS responds in 524 ms versus TheMealDB at 198 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 LAPIS and TheMealDB need an API key?

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

Can I call LAPIS and TheMealDB from the browser?

Yes — both LAPIS and TheMealDB 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 TheMealDB free for commercial use?

LAPIS has unclear commercial terms, and TheMealDB 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.