shipapis
StarSubmit an APISubmit API

Cartes.io vs OpenPLZ API

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

APICartes.ioHEALTHY92OpenPLZ APIHEALTHY94
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms612561
P95 · ms1160903
Authnonenone
CORSyesyes
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 OpenPLZ API: common questions

Which is more reliable, Cartes.io or OpenPLZ API?

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

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

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

Can I call Cartes.io and OpenPLZ API from the browser?

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

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