shipapis
StarSubmit an APISubmit API

airportsapi vs NHTSA

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

APIairportsapiNEW—NHTSANEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedPublic domain (U.S. Government work)
Free tierFree — limits not publishedFree, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

airportsapi vs NHTSA: common questions

Which is more reliable, airportsapi or NHTSA?

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

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

Can I call airportsapi and NHTSA from the browser?

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

airportsapi has unclear commercial terms, and NHTSA allows commercial use on its free tier. 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.