ClinicalTrials.gov vs Lexigram

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
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?

On our scheduled checks, Lexigram leads on measured uptime — ClinicalTrials.gov at —% versus Lexigram 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 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.