Cartes.io vs Loket.nl API

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms612361
P95 · ms11601039
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 Loket.nl API: common questions

Which is more reliable, Cartes.io or Loket.nl API?

On our scheduled checks, Loket.nl API leads on measured uptime — Cartes.io at 99.02% versus Loket.nl API at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Cartes.io or Loket.nl API?

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

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

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

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

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