Cartes.io vs Metadapi Zip Code

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
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 Metadapi Zip Code: common questions

Which is more reliable, Cartes.io or Metadapi Zip Code?

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

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

Can I call Cartes.io and Metadapi Zip Code from the browser?

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

Are Cartes.io and Metadapi Zip Code free for commercial use?

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