IBM X-Force Exchange API vs IP Geolocation API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBM X-Force Exchange API vs IP Geolocation API: common questions

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

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

IP Geolocation 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 IP Geolocation API first.

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

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

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