CheapShark API vs OpenSanctions

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
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

CheapShark API vs OpenSanctions: common questions

Which is more reliable, CheapShark API or OpenSanctions?

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

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

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

Are CheapShark API and OpenSanctions free for commercial use?

CheapShark API 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.