shipapis
StarSubmit an APISubmit API

Openwhyd vs SWAPI GraphQL

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

APIOpenwhydNEW—SWAPI GraphQLNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Openwhyd vs SWAPI GraphQL: common questions

Which is more reliable, Openwhyd or SWAPI GraphQL?

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

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

Can I call Openwhyd and SWAPI GraphQL from the browser?

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

Are Openwhyd and SWAPI GraphQL free for commercial use?

Openwhyd has unclear commercial terms, and SWAPI GraphQL 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.