Currents vs Lookup.im API
Same instrument, two spec sheets — measured, not claimed.
Currents vs Lookup.im API: common questions
Which is more reliable, Currents or Lookup.im API?
On our scheduled checks, Currents leads on measured uptime — Currents at 100% versus Lookup.im API at 99.02% 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, Currents or Lookup.im API?
Currents has the lower median latency in our checks — Currents responds in 586 ms versus Lookup.im API at 1158 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 Currents and Lookup.im API need an API key?
Both ask you to authenticate — Currents 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 Currents and Lookup.im API from the browser?
Neither sends browser-friendly CORS headers reliably, so call Currents and Lookup.im API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.
Are Currents and Lookup.im API free for commercial use?
Currents 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.