OkSurf vs OpenSanctions

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms624387
P95 · ms18704183
Authnonenone
CORSnoyes
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

OkSurf vs OpenSanctions: common questions

Which is more reliable, OkSurf or OpenSanctions?

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

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

Neither needs a paid key — OkSurf 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 OkSurf and OpenSanctions from the browser?

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

Are OkSurf and OpenSanctions free for commercial use?

OkSurf 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.