SWAPI GraphQL vs xColors

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

SWAPI GraphQL vs xColors: common questions

Which is more reliable, SWAPI GraphQL or xColors?

On our scheduled checks, xColors leads on measured uptime — SWAPI GraphQL at —% versus xColors 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 SWAPI GraphQL and xColors need an API key?

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

Yes — both SWAPI GraphQL 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 SWAPI GraphQL and xColors free for commercial use?

SWAPI GraphQL 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.