Discogs vs TMDb

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

Uptime · 30d
Uptime · 90d2.2%100%
Uptime · 30d0.0%100%
P50 · ms231105
P95 · ms3521432
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearno
Data licenseUnverifiedTMDb terms — attribution required
Free tierFree — limits not publishedFree personal API key
Rate limitUnpublished~50 req/sec documented ceiling
In directory since2026-07-052026-07-05
operationalpartialdownno data

Discogs vs TMDb: common questions

Which is more reliable, Discogs or TMDb?

On our scheduled checks, TMDb leads on measured uptime — Discogs at 2.2% versus TMDb 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, Discogs or TMDb?

TMDb has the lower median latency in our checks — Discogs responds in 231 ms versus TMDb at 105 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 Discogs and TMDb need an API key?

Discogs needs no key, while TMDb requires a free API key. If you want to start calling without signup, reach for Discogs first.

Can I call Discogs and TMDb from the browser?

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

Are Discogs and TMDb free for commercial use?

Discogs has unclear commercial terms, and TMDb is personal/non-commercial only. 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.