shipapis
StarSubmit an APISubmit API

ClinicalTrials.gov vs Makeup

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

APIClinicalTrials.govHEALTHY77MakeupHEALTHY87
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%100%
P50 · ms243791
P95 · ms5742529
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ClinicalTrials.gov vs Makeup: common questions

Which is more reliable, ClinicalTrials.gov or Makeup?

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

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

Neither needs a paid key — ClinicalTrials.gov is callable with no signup, and Makeup is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

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

Are ClinicalTrials.gov and Makeup free for commercial use?

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