Micro User Service vs OpenSanctions

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

Uptime · 30d
Uptime · 90d18.6%100%
Uptime · 30d0.0%100%
P50 · ms231387
P95 · ms8274183
AuthapiKeynone
CORSnoyes
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

Micro User Service vs OpenSanctions: common questions

Which is more reliable, Micro User Service or OpenSanctions?

On our scheduled checks, OpenSanctions leads on measured uptime — Micro User Service at 18.6% 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.

Which is faster, Micro User Service or OpenSanctions?

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

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

Can I call Micro User Service and OpenSanctions from the browser?

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

Are Micro User Service and OpenSanctions free for commercial use?

Micro User Service 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.