OpenSanctions vs RSS2JSON

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenSanctions vs RSS2JSON: common questions

Which is more reliable, OpenSanctions or RSS2JSON?

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

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

Can I call OpenSanctions and RSS2JSON from the browser?

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

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