shipapis
StarSubmit an APISubmit API

OpenSanctions vs Warnely

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

APIOpenSanctionsNEW—WarnelyNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenSanctions vs Warnely: common questions

Which is more reliable, OpenSanctions or Warnely?

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

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

Can I call OpenSanctions and Warnely from the browser?

Yes — both OpenSanctions and Warnely 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 OpenSanctions and Warnely free for commercial use?

OpenSanctions has unclear commercial terms, and Warnely 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.