Kaggle vs OpenSanctions

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms250387
P95 · ms5664183
AuthapiKeynone
CORSyesyes
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

Kaggle vs OpenSanctions: common questions

Which is more reliable, Kaggle or OpenSanctions?

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

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

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

Can I call Kaggle and OpenSanctions from the browser?

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

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