shipapis
StarSubmit an APISubmit API

ClinicalTrials.gov vs Lexigram

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

APIClinicalTrials.govHEALTHY77LexigramHEALTHY88
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms243807
P95 · ms5741672
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ClinicalTrials.gov vs Lexigram: common questions

Which is more reliable, ClinicalTrials.gov or Lexigram?

Both are neck-and-neck — ClinicalTrials.gov and Lexigram 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, ClinicalTrials.gov or Lexigram?

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

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

Can I call ClinicalTrials.gov and Lexigram from the browser?

Only ClinicalTrials.gov 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 ClinicalTrials.gov and Lexigram free for commercial use?

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