ColorMagic vs Harry Potter API

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

Uptime · 30d
Uptime · 90d83.9%100%
Uptime · 30d51.7%100%
P50 · ms267154
P95 · ms3070795
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ColorMagic vs Harry Potter API: common questions

Which is more reliable, ColorMagic or Harry Potter API?

On our scheduled checks, Harry Potter API leads on measured uptime — ColorMagic at 83.9% versus Harry Potter API 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, ColorMagic or Harry Potter API?

Harry Potter API has the lower median latency in our checks — ColorMagic responds in 267 ms versus Harry Potter API at 154 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 ColorMagic and Harry Potter API need an API key?

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

Can I call ColorMagic and Harry Potter API from the browser?

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

Are ColorMagic and Harry Potter API free for commercial use?

ColorMagic has unclear commercial terms, and Harry Potter API 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.