PostalPinCode vs OpenVan

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree — no auth
Rate limitUnpublished120 req/window · 119 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

PostalPinCode vs OpenVan: common questions

Which is more reliable, PostalPinCode or OpenVan?

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

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

Can I call PostalPinCode and OpenVan from the browser?

Yes — both PostalPinCode and OpenVan send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are PostalPinCode and OpenVan free for commercial use?

PostalPinCode has unclear commercial terms, and OpenVan 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.