The Office API vs xColors

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms1459642
P95 · ms24681161
Authnonenone
CORSyesyes
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

The Office API vs xColors: common questions

Which is more reliable, The Office API or xColors?

On our scheduled checks, xColors leads on measured uptime — The Office API at 99.02% 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, The Office API or xColors?

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

Neither needs a paid key — The Office API 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 The Office API and xColors from the browser?

Yes — both The Office API 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 The Office API and xColors free for commercial use?

The Office API 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.