shipapis
StarSubmit an APISubmit API

IBM X-Force Exchange API vs Open VSX Registry API

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

APIIBM X-Force Exchange APINEW—Open VSX Registry APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished10800 req/window · 10799 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBM X-Force Exchange API vs Open VSX Registry API: common questions

Which is more reliable, IBM X-Force Exchange API or Open VSX Registry API?

On our scheduled checks, Open VSX Registry API leads on measured uptime — IBM X-Force Exchange API at —% versus Open VSX Registry API at —% 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 IBM X-Force Exchange API and Open VSX Registry API need an API key?

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

Can I call IBM X-Force Exchange API and Open VSX Registry API from the browser?

Only Open VSX Registry API 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 Open VSX Registry API free for commercial use?

IBM X-Force Exchange API has unclear commercial terms, and Open VSX Registry 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.