OpenSanctions vs Stytch

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms387577
P95 · ms41831314
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenSanctions vs Stytch: common questions

Which is more reliable, OpenSanctions or Stytch?

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

OpenSanctions has the lower median latency in our checks — OpenSanctions responds in 387 ms versus Stytch at 577 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 OpenSanctions and Stytch need an API key?

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

Can I call OpenSanctions and Stytch from the browser?

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

Are OpenSanctions and Stytch free for commercial use?

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