GeoJS vs VA Facilities

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1071386
P95 · ms7223391
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API key requiredFree tier — API key required
Rate limitUnpublished (no enforced limit stated)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoJS vs VA Facilities: common questions

Which is more reliable, GeoJS or VA Facilities?

Both are neck-and-neck — GeoJS and VA Facilities each measure 100% 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, GeoJS or VA Facilities?

GeoJS has the lower median latency in our checks — GeoJS responds in 107 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 GeoJS and VA Facilities need an API key?

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

Can I call GeoJS and VA Facilities from the browser?

Only GeoJS 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 GeoJS and VA Facilities free for commercial use?

GeoJS 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.