NHTSA vs OpenVan

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms760864
P95 · ms49022707
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licensePublic domain (U.S. Government work)Unverified
Free tierFree, no keyFree — no auth
Rate limitUnpublished120 req/window · 119 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

NHTSA vs OpenVan: common questions

Which is more reliable, NHTSA or OpenVan?

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

Which is faster, NHTSA or OpenVan?

NHTSA has the lower median latency in our checks — NHTSA responds in 760 ms versus OpenVan at 864 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do NHTSA and OpenVan need an API key?

Neither needs a paid key — NHTSA 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 NHTSA and OpenVan from the browser?

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

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