Currents vs RestoSignals
Same instrument, two spec sheets — measured, not claimed.
Currents vs RestoSignals: common questions
Which is more reliable, Currents or RestoSignals?
Both are neck-and-neck — Currents and RestoSignals 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 RestoSignals?
Currents has the lower median latency in our checks — Currents responds in 291 ms versus RestoSignals at 748 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 RestoSignals need an API key?
Both ask you to authenticate — Currents uses an API key and RestoSignals 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 RestoSignals from the browser?
Neither sends browser-friendly CORS headers reliably, so call Currents and RestoSignals 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 RestoSignals free for commercial use?
Currents has unclear commercial terms, and RestoSignals 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.