NHTSA vs Transport for United States

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licensePublic domain (U.S. Government work)Data copyright transit agencies / Umo IQ
Free tierFree, no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

NHTSA vs Transport for United States: common questions

Which is more reliable, NHTSA or Transport for United States?

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

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

Can I call NHTSA and Transport for United States from the browser?

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

NHTSA allows commercial use on its free tier, and Transport for United States 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.