Currents vs OpenSanctions
Same instrument, two spec sheets — measured, not claimed.
Currents vs OpenSanctions: common questions
Which is more reliable, Currents or OpenSanctions?
Both are neck-and-neck — Currents and OpenSanctions each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.
Which is faster, Currents or OpenSanctions?
OpenSanctions has the lower median latency in our checks — Currents responds in 586 ms versus OpenSanctions at 387 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.
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.