shipapis
StarSubmit an APISubmit API

OpenCorporates vs OWASP API Security Project

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

APIOpenCorporatesNEW—OWASP API Security ProjectNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenCorporates vs OWASP API Security Project: common questions

Which is more reliable, OpenCorporates or OWASP API Security Project?

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

OWASP API Security Project needs no key, while OpenCorporates requires a free API key. If you want to start calling without signup, reach for OWASP API Security Project first.

Can I call OpenCorporates and OWASP API Security Project from the browser?

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

Are OpenCorporates and OWASP API Security Project free for commercial use?

OpenCorporates has unclear commercial terms, and OWASP API Security Project 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.