Cartes.io vs VA Facilities

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms6121386
P95 · ms11603391
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 VA Facilities: common questions

Which is more reliable, Cartes.io or VA Facilities?

On our scheduled checks, VA Facilities leads on measured uptime — Cartes.io at 99.02% versus VA Facilities 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 VA Facilities?

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

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

Can I call Cartes.io and VA Facilities from the browser?

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

Are Cartes.io and VA Facilities free for commercial use?

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