shipapis
StarSubmit an APISubmit API

OpenSanctions vs Wikipedia REST

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

APIOpenSanctionsNEW—Wikipedia RESTHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY-SA 4.0
Free tierFree — limits not publishedUnlimited within etiquette
Rate limitUnpublished200/sec global courtesy cap
In directory since2026-07-052026-05-09
operationalpartialdownno data

OpenSanctions vs Wikipedia REST: common questions

Which is more reliable, OpenSanctions or Wikipedia REST?

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

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

Can I call OpenSanctions and Wikipedia REST from the browser?

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

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