shipapis
StarSubmit an APISubmit API

Currents vs OpenSanctions

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

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

Currents vs OpenSanctions: common questions

Which is more reliable, Currents or OpenSanctions?

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

OpenSanctions needs no key, while Currents requires a free API key. If you want to start calling without signup, reach for OpenSanctions first.

Can I call Currents and OpenSanctions from the browser?

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

Are Currents and OpenSanctions free for commercial use?

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