shipapis
StarSubmit an APISubmit API

Lexigram vs Open Disease

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

APILexigramHEALTHY88Open DiseaseHEALTHY94
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms807451
P95 · ms16721226
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (sources vary; see project repo)
Free tierFree tier — key may be requiredFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lexigram vs Open Disease: common questions

Which is more reliable, Lexigram or Open Disease?

Both are neck-and-neck — Lexigram and Open Disease each measure 99.02% 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, Lexigram or Open Disease?

Open Disease has the lower median latency in our checks — Lexigram responds in 807 ms versus Open Disease at 451 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 Lexigram and Open Disease need an API key?

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

Can I call Lexigram and Open Disease from the browser?

Only Open Disease is browser-friendly — it returns CORS headers over HTTPS. Lexigram needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Lexigram and Open Disease free for commercial use?

Lexigram has unclear commercial terms, and Open Disease 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.