shipapis
StarSubmit an APISubmit API

LAPIS vs SharpAPI

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

APILAPISNEW—SharpAPINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseOpen sequence data (GenBank/Nextstrain-derived); UnverifiedUnverified
Free tierFree — no key (open instance)Free tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LAPIS vs SharpAPI: common questions

Which is more reliable, LAPIS or SharpAPI?

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

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

Can I call LAPIS and SharpAPI from the browser?

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

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