Data Dragon API vs Fruityvice

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms153951
P95 · ms14283996
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

Data Dragon API vs Fruityvice: common questions

Which is more reliable, Data Dragon API or Fruityvice?

Both are neck-and-neck — Data Dragon API 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, Data Dragon API or Fruityvice?

Data Dragon API has the lower median latency in our checks — Data Dragon API responds in 153 ms versus Fruityvice at 951 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 Data Dragon API and Fruityvice need an API key?

Neither needs a paid key — Data Dragon API 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 Data Dragon API and Fruityvice from the browser?

Only Data Dragon API 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 Data Dragon API and Fruityvice free for commercial use?

Data Dragon API 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.