positionstack vs Smappee API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

positionstack vs Smappee API: common questions

Which is more reliable, positionstack or Smappee API?

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

Do positionstack and Smappee API need an API key?

Both ask you to authenticate — positionstack uses an API key and Smappee API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call positionstack and Smappee API from the browser?

Neither sends browser-friendly CORS headers reliably, so call positionstack and Smappee API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are positionstack and Smappee API free for commercial use?

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