shipapis
StarSubmit an APISubmit API

RecipeAPI vs LAPIS

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

APIRecipeAPIUNMONITORED—LAPISNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedOpen sequence data (GenBank/Nextstrain-derived); Unverified
Free tierFree tier — API key requiredFree — no key (open instance)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

RecipeAPI vs LAPIS: common questions

Which is more reliable, RecipeAPI 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 RecipeAPI and LAPIS need an API key?

LAPIS needs no key, while RecipeAPI requires a free API key. If you want to start calling without signup, reach for LAPIS first.

Can I call RecipeAPI and LAPIS from the browser?

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

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