OpenCorporates vs RestoSignals

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d0.0%100%
Uptime · 30d0.0%100%
P50 · ms—748
P95 · ms—748
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — API key required
Rate limitUnpublished
In directory since2026-07-052026-10-19
operationalpartialdownno data

OpenCorporates vs RestoSignals: common questions

Which is more reliable, OpenCorporates or RestoSignals?

On our scheduled checks, RestoSignals leads on measured uptime — OpenCorporates at 0.0% versus RestoSignals 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.

Do OpenCorporates and RestoSignals need an API key?

Both ask you to authenticate — OpenCorporates 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 OpenCorporates and RestoSignals from the browser?

Neither sends browser-friendly CORS headers reliably, so call OpenCorporates 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 OpenCorporates and RestoSignals free for commercial use?

OpenCorporates 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.