shipapis
StarSubmit an APISubmit API

ClinicalTrials.gov vs Fruityvice

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

APIClinicalTrials.govHEALTHY78FruityviceHEALTHY92
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms138448
P95 · ms35332603
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no API key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ClinicalTrials.gov vs Fruityvice: common questions

Which is more reliable, ClinicalTrials.gov or Fruityvice?

Both are neck-and-neck — ClinicalTrials.gov and Fruityvice each measure 100% 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 Fruityvice?

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

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

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

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

Are ClinicalTrials.gov and Fruityvice free for commercial use?

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