shipapis
StarSubmit an APISubmit API

ApogeoAPI vs Cartes.io

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

APIApogeoAPINEW—Cartes.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source project; user-generated maps)
Free tierFree tier — API key requiredFree, no API key for public read
Rate limitUnpublished60 req/window · 59 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

ApogeoAPI vs Cartes.io: common questions

Which is more reliable, ApogeoAPI or Cartes.io?

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

Cartes.io needs no key, while ApogeoAPI requires a free API key. If you want to start calling without signup, reach for Cartes.io first.

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

Only Cartes.io is browser-friendly — it returns CORS headers over HTTPS. ApogeoAPI needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are ApogeoAPI and Cartes.io free for commercial use?

ApogeoAPI 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.