BdAPIs vs IPGEO

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API keyFree — limits not published
Rate limit100 req/window · 98 remaining · resets 324Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BdAPIs vs IPGEO: common questions

Which is more reliable, BdAPIs or IPGEO?

On our scheduled checks, IPGEO leads on measured uptime — BdAPIs at —% versus IPGEO 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 BdAPIs and IPGEO need an API key?

Neither needs a paid key — BdAPIs is callable with no signup, and IPGEO is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call BdAPIs and IPGEO from the browser?

Yes — both BdAPIs and IPGEO send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are BdAPIs and IPGEO free for commercial use?

BdAPIs has unclear commercial terms, and IPGEO 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.