OpenSanctions vs Voidly

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0
Free tierFree — limits not publishedFree (keyless data endpoints; Hydra ML endpoints need a key)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenSanctions vs Voidly: common questions

Which is more reliable, OpenSanctions or Voidly?

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

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

Can I call OpenSanctions and Voidly from the browser?

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

OpenSanctions has unclear commercial terms, and Voidly allows commercial use on its free tier. 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.