ICD-10 Codes vs LAPIS

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1831524
P95 · ms3898846
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

ICD-10 Codes vs LAPIS: common questions

Which is more reliable, ICD-10 Codes or LAPIS?

Both are neck-and-neck — ICD-10 Codes and LAPIS 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, ICD-10 Codes or LAPIS?

LAPIS has the lower median latency in our checks — ICD-10 Codes responds in 1831 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 ICD-10 Codes and LAPIS need an API key?

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

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

ICD-10 Codes 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.