shipapis
StarSubmit an APISubmit API

OWASP API Security Project vs Registrum API

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

APIOWASP API Security ProjectNEW—Registrum APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OWASP API Security Project vs Registrum API: common questions

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

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

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

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

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

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

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