Currents vs Registrum API
Same instrument, two spec sheets — measured, not claimed.
Currents vs Registrum API: common questions
Which is more reliable, Currents or Registrum API?
Both are neck-and-neck — Currents and Registrum API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.
Which is faster, Currents or Registrum API?
Registrum API has the lower median latency in our checks — Currents responds in 586 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 Currents and Registrum API need an API key?
Both ask you to authenticate — Currents 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 Currents and Registrum API from the browser?
Neither sends browser-friendly CORS headers reliably, so call Currents and Registrum 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 Registrum API free for commercial use?
Currents 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.