shipapis
StarSubmit an APISubmit API

Geocode.xyz vs positionstack

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

APIGeocode.xyzHEALTHY76positionstackHEALTHY93
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms386455
P95 · ms6043328
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geocode.xyz vs positionstack: common questions

Which is more reliable, Geocode.xyz or positionstack?

Both are neck-and-neck — Geocode.xyz and positionstack 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, Geocode.xyz or positionstack?

Geocode.xyz has the lower median latency in our checks — Geocode.xyz responds in 386 ms versus positionstack at 455 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 Geocode.xyz and positionstack need an API key?

Geocode.xyz needs no key, while positionstack requires a free API key. If you want to start calling without signup, reach for Geocode.xyz first.

Can I call Geocode.xyz and positionstack from the browser?

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

Are Geocode.xyz and positionstack free for commercial use?

Geocode.xyz has unclear commercial terms, and positionstack 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.