Court Rules vs OpenSanctions

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

Uptime · 30d
Uptime · 90d0.0%100%
Uptime · 30d0.0%100%
P50 · ms—170
P95 · ms—4183
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-10-042026-07-05
operationalpartialdownno data

Court Rules vs OpenSanctions: common questions

Which is more reliable, Court Rules or OpenSanctions?

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

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

Can I call Court Rules and OpenSanctions from the browser?

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

Are Court Rules and OpenSanctions free for commercial use?

Court Rules 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.