ClinicalTrials.gov vs Open Disease
Same instrument, two spec sheets — measured, not claimed.
ClinicalTrials.gov vs Open Disease: common questions
Which is more reliable, ClinicalTrials.gov or Open Disease?
On our scheduled checks, ClinicalTrials.gov leads on measured uptime — ClinicalTrials.gov at 100% versus Open Disease at 99.44% 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, ClinicalTrials.gov or Open Disease?
ClinicalTrials.gov has the lower median latency in our checks — ClinicalTrials.gov responds in 138 ms versus Open Disease at 217 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 Open Disease need an API key?
Neither needs a paid key — ClinicalTrials.gov is callable with no signup, and Open Disease is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call ClinicalTrials.gov and Open Disease from the browser?
Yes — both ClinicalTrials.gov and Open Disease 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 ClinicalTrials.gov and Open Disease free for commercial use?
ClinicalTrials.gov 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.