Invokely vs OpenSanctions

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms227170
P95 · ms2454183
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-10-122026-07-05
operationalpartialdownno data

Invokely vs OpenSanctions: common questions

Which is more reliable, Invokely or OpenSanctions?

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

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

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

Can I call Invokely and OpenSanctions from the browser?

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

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