shipapis
StarSubmit an APISubmit API

TheCocktailDB vs LAPIS

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

APITheCocktailDBNEW—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

TheCocktailDB vs LAPIS: common questions

Which is more reliable, TheCocktailDB or LAPIS?

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

Neither needs a paid key — TheCocktailDB 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 TheCocktailDB and LAPIS from the browser?

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

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