Foodish vs TheSportsDB

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

Uptime · 30d
Uptime · 90d27.5%55.9%
Uptime · 30d11.7%56.7%
P50 · ms250238
P95 · ms7603182
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source)Unverified
Free tierFree — no keyFree — limits not published
Rate limitUnpublishedRetry-After: 92s
In directory since2026-07-052026-07-05
operationalpartialdownno data

Foodish vs TheSportsDB: common questions

Which is more reliable, Foodish or TheSportsDB?

On our scheduled checks, TheSportsDB leads on measured uptime — Foodish at 27.5% versus TheSportsDB at 55.9% 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, Foodish or TheSportsDB?

TheSportsDB has the lower median latency in our checks — Foodish responds in 250 ms versus TheSportsDB at 238 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 Foodish and TheSportsDB need an API key?

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

Can I call Foodish and TheSportsDB from the browser?

Neither sends browser-friendly CORS headers reliably, so call Foodish and TheSportsDB from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Foodish and TheSportsDB free for commercial use?

Foodish has unclear commercial terms, and TheSportsDB 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.