shipapis
StarSubmit an APISubmit API

NHTSA vs PostalPinCode

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

APINHTSANEW—PostalPinCodeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licensePublic domain (U.S. Government work)Unverified
Free tierFree, no keyFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

NHTSA vs PostalPinCode: common questions

Which is more reliable, NHTSA or PostalPinCode?

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

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

Can I call NHTSA and PostalPinCode from the browser?

Yes — both NHTSA and PostalPinCode 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 NHTSA and PostalPinCode free for commercial use?

NHTSA allows commercial use on its free tier, and PostalPinCode 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.