shipapis
StarSubmit an APISubmit API

Postcodes.io vs Visitor Statistics API

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

APIPostcodes.ioNEW—Visitor Statistics APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseService MIT-licensed; postcode data license unverifiedUnverified
Free tierFree — no key requiredFree — limits not published
Rate limitUnpublished (no key; fair use)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Postcodes.io vs Visitor Statistics API: common questions

Which is more reliable, Postcodes.io or Visitor Statistics API?

On our scheduled checks, Visitor Statistics API leads on measured uptime — Postcodes.io at —% versus Visitor Statistics 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 Postcodes.io and Visitor Statistics API need an API key?

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

Can I call Postcodes.io and Visitor Statistics API from the browser?

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

Are Postcodes.io and Visitor Statistics API free for commercial use?

Postcodes.io has unclear commercial terms, and Visitor Statistics 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.