IBM X-Force Exchange API vs RestoSignals

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

Uptime · 30d
Uptime · 90d96.7%100%
Uptime · 30d93.3%100%
P50 · ms198748
P95 · ms1401748
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

IBM X-Force Exchange API vs RestoSignals: common questions

Which is more reliable, IBM X-Force Exchange API or RestoSignals?

On our scheduled checks, RestoSignals leads on measured uptime — IBM X-Force Exchange API at 96.7% 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.

Which is faster, IBM X-Force Exchange API or RestoSignals?

IBM X-Force Exchange API has the lower median latency in our checks — IBM X-Force Exchange API responds in 198 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 IBM X-Force Exchange API and RestoSignals need an API key?

Both ask you to authenticate — IBM X-Force Exchange API 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 IBM X-Force Exchange API and RestoSignals from the browser?

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

IBM X-Force Exchange API 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.