CIRCL CVE Search vs Registrum API
Same instrument, two spec sheets — measured, not claimed.
CIRCL CVE Search vs Registrum API: common questions
Which is more reliable, CIRCL CVE Search or Registrum API?
On our scheduled checks, Registrum API leads on measured uptime — CIRCL CVE Search at 98.0% versus Registrum API at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, CIRCL CVE Search or Registrum API?
Registrum API has the lower median latency in our checks — CIRCL CVE Search responds in 698 ms versus Registrum API at 246 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 CIRCL CVE Search and Registrum API need an API key?
Both ask you to authenticate — CIRCL CVE Search uses an API key and Registrum API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.
Can I call CIRCL CVE Search and Registrum API from the browser?
Only CIRCL CVE Search 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 CIRCL CVE Search and Registrum API free for commercial use?
CIRCL CVE Search 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.