shipapis
StarSubmit an APISubmit API

Cartes.io vs US ZipCode

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

APICartes.ioNEW—US ZipCodeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
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 US ZipCode: common questions

Which is more reliable, Cartes.io or US ZipCode?

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

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

Can I call Cartes.io and US ZipCode from the browser?

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

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