TMDb vs xColors

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms352642
P95 · ms15281161
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial usenounclear
Data licenseTMDb terms — attribution requiredUnverified
Free tierFree personal API keyFree — limits not published
Rate limit~50 req/sec documented ceilingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

TMDb vs xColors: common questions

Which is more reliable, TMDb or xColors?

Both are neck-and-neck — TMDb and xColors 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, TMDb or xColors?

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

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

Can I call TMDb and xColors from the browser?

Yes — both TMDb and xColors send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are TMDb and xColors free for commercial use?

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