shipapis
StarSubmit an APISubmit API

CIE-10 API vs LAPIS

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

APICIE-10 APIHEALTHY91LAPISHEALTHY95
Uptime · 30d
Uptime · 90d94.1%100%
Uptime · 30d100%100%
P50 · ms466524
P95 · ms991846
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 limit120 req/window · 119 remaining · resets 1783518425Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CIE-10 API vs LAPIS: common questions

Which is more reliable, CIE-10 API or LAPIS?

On our scheduled checks, LAPIS leads on measured uptime — CIE-10 API at 94.1% versus LAPIS at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, CIE-10 API or LAPIS?

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

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

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

CIE-10 API 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.