Apify vs OpenSanctions

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms381387
P95 · ms7654183
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Apify vs OpenSanctions: common questions

Which is more reliable, Apify or OpenSanctions?

Both are neck-and-neck — Apify 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, Apify or OpenSanctions?

Apify has the lower median latency in our checks — Apify responds in 381 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 Apify and OpenSanctions need an API key?

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

Can I call Apify and OpenSanctions from the browser?

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

Are Apify and OpenSanctions free for commercial use?

Apify 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.