shipapis
StarSubmit an APISubmit API

PostalCodes vs GeoJS

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

APIPostalCodesNEW—GeoJSNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree, no API key required
Rate limitUnpublishedUnpublished (no enforced limit stated)
In directory since2026-07-052026-07-05
operationalpartialdownno data

PostalCodes vs GeoJS: common questions

Which is more reliable, PostalCodes or GeoJS?

On our scheduled checks, GeoJS leads on measured uptime — PostalCodes at —% versus GeoJS 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 PostalCodes and GeoJS need an API key?

Neither needs a paid key — PostalCodes is callable with no signup, and GeoJS is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call PostalCodes and GeoJS from the browser?

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

Are PostalCodes and GeoJS free for commercial use?

PostalCodes has unclear commercial terms, and GeoJS 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.