shipapis
StarSubmit an APISubmit API

Cartes.io vs PostalCodes

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

APICartes.ioHEALTHY92PostalCodesHEALTHY84
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms6121030
P95 · ms11602594
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source project; user-generated maps)Unverified
Free tierFree, no API key for public readFree — limits not published
Rate limit60 req/window · 59 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cartes.io vs PostalCodes: common questions

Which is more reliable, Cartes.io or PostalCodes?

Both are neck-and-neck — Cartes.io and PostalCodes 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 PostalCodes?

Cartes.io has the lower median latency in our checks — Cartes.io responds in 612 ms versus PostalCodes at 1030 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 PostalCodes need an API key?

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

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

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

Are Cartes.io and PostalCodes free for commercial use?

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