TMDb vs Trakt

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial usenounclear
Data licenseTMDb terms — attribution requiredTrakt terms — user-contributed data
Free tierFree personal API keyFree OAuth application
Rate limit~50 req/sec documented ceiling1,000 req every 5 min documented
In directory since2026-07-052026-07-05
operationalpartialdownno data

TMDb vs Trakt: common questions

Which is more reliable, TMDb or Trakt?

On our scheduled checks, Trakt leads on measured uptime — TMDb at —% versus Trakt at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do TMDb and Trakt need an API key?

Both ask you to authenticate — TMDb uses an API key and Trakt uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call TMDb and Trakt from the browser?

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

Are TMDb and Trakt free for commercial use?

TMDb is personal/non-commercial only, and Trakt 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.