iTunes Search vs xColors

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

Uptime · 30d
Uptime · 90d5.9%100%
Uptime · 30d5.0%100%
P50 · ms233642
P95 · ms2931161
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitRetry-After: 29sUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

iTunes Search vs xColors: common questions

Which is more reliable, iTunes Search or xColors?

On our scheduled checks, xColors leads on measured uptime — iTunes Search at 5.9% versus xColors 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, iTunes Search or xColors?

iTunes Search has the lower median latency in our checks — iTunes Search responds in 233 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 iTunes Search and xColors need an API key?

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

Can I call iTunes Search and xColors from the browser?

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

Are iTunes Search and xColors free for commercial use?

iTunes Search has unclear commercial terms, 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.