IBM X-Force Exchange API vs Voidly

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

Uptime · 30d
Uptime · 90d96.7%86.0%
Uptime · 30d93.3%81.0%
P50 · ms1981865
P95 · ms14014655
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0
Free tierFree tier — API key requiredFree (keyless data endpoints; Hydra ML endpoints need a key)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBM X-Force Exchange API vs Voidly: common questions

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

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

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

Voidly needs no key, while IBM X-Force Exchange API requires a free API key. If you want to start calling without signup, reach for Voidly first.

Can I call IBM X-Force Exchange API and Voidly from the browser?

Only Voidly is browser-friendly — it returns CORS headers over HTTPS. IBM X-Force Exchange API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are IBM X-Force Exchange API and Voidly free for commercial use?

IBM X-Force Exchange API has unclear commercial terms, and Voidly allows commercial use on its free tier. 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.