Cartes.io vs Geocodify.com

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%100%
P50 · ms612615
P95 · ms11602409
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source project; user-generated maps)Unverified
Free tierFree, no API key for public readFree tier — API key required
Rate limit60 req/window · 59 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cartes.io vs Geocodify.com: common questions

Which is more reliable, Cartes.io or Geocodify.com?

Both are neck-and-neck — Cartes.io and Geocodify.com each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Cartes.io or Geocodify.com?

Cartes.io has the lower median latency in our checks — Cartes.io responds in 612 ms versus Geocodify.com at 615 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Cartes.io and Geocodify.com need an API key?

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

Can I call Cartes.io and Geocodify.com from the browser?

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

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