Openwhyd vs ThronesApi

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

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

Openwhyd vs ThronesApi: common questions

Which is more reliable, Openwhyd or ThronesApi?

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

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

Can I call Openwhyd and ThronesApi from the browser?

Only ThronesApi 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 ThronesApi free for commercial use?

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