Coffee vs Data Dragon API

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms698153
P95 · ms28261428
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Coffee vs Data Dragon API: common questions

Which is more reliable, Coffee or Data Dragon API?

On our scheduled checks, Data Dragon API leads on measured uptime — Coffee at 99.02% versus Data Dragon API at 100% 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, Coffee or Data Dragon API?

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

Neither needs a paid key — Coffee is callable with no signup, and Data Dragon API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Coffee and Data Dragon API from the browser?

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

Are Coffee and Data Dragon API free for commercial use?

Coffee has unclear commercial terms, and Data Dragon API 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.