BdAPIs vs Cartes.io

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 (open-source project; user-generated maps)
Free tierFree, no API keyFree, no API key for public read
Rate limit100 req/window · 98 remaining · resets 32460 req/window · 59 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

BdAPIs vs Cartes.io: common questions

Which is more reliable, BdAPIs or Cartes.io?

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

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

Can I call BdAPIs and Cartes.io from the browser?

Yes — both BdAPIs and Cartes.io 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 Cartes.io free for commercial use?

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