CIRCL CVE Search vs Lookup.im API
Same instrument, two spec sheets — measured, not claimed.
CIRCL CVE Search vs Lookup.im API: common questions
Which is more reliable, CIRCL CVE Search or Lookup.im API?
On our scheduled checks, Lookup.im API leads on measured uptime — CIRCL CVE Search at 96.1% versus Lookup.im API at 97.8% 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 Lookup.im API?
Lookup.im API has the lower median latency in our checks — CIRCL CVE Search responds in 503 ms versus Lookup.im API at 180 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 Lookup.im API need an API key?
Both ask you to authenticate — CIRCL CVE Search uses an API key and Lookup.im 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 Lookup.im API from the browser?
Only CIRCL CVE Search is browser-friendly — it returns CORS headers over HTTPS. Lookup.im API needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are CIRCL CVE Search and Lookup.im API free for commercial use?
CIRCL CVE Search has unclear commercial terms, and Lookup.im 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.