Live US airport delays for travel & logistics AI.
A travel or logistics agent needs to know if US airspace is disrupted — sourced and current. Dynamic Feed serves the FAA's National Airspace System status keyless over MCP or REST, each response signed and timestamped.
The call
Keyless over MCP, or one REST call with a free key. Every datapoint is provenance-stamped and citeable.
# Keyless — one signed call over REST:
curl -s https://dynamicfeed.ai/v1/batch -H "Content-Type: application/json" \
-d '{"calls":[{"tool":"airport_delays","args":{}}]}'
# MCP (keyless) — point any client at https://dynamicfeed.ai/mcp, then call airport_delays()Sample response
{ "count": 0, "results": [], "source": "FAA NAS Status", "observed_at": "...Z",
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-4cb32e72f333" } }Why live data
Dynamic Feed serves the FAA's National Airspace System status — airport closures, ground stops, ground-delay programs and arrival/departure delays — in a provenance envelope, signed over its exact bytes and verifiable against /.well-known/keys. Scope is US airspace (FAA) only. An empty or short list means the airspace is running normally — a valid state, not an error. It surfaces what the FAA published at a time and is not a guarantee of completeness.
Use it for
- Ground a travel / logistics agent in live US airspace status
- A signed record of delay / ground-stop conditions at a point in time
- Ops workflows that route around disruptions, citeably
- Pairs with live flight tracking and weather feeds
FAQ
What does it cover?
The US National Airspace System (FAA) — closures, ground stops, ground-delay programs and arrival/departure delays. It does not cover non-US airspace.
Does an empty list mean it's broken?
No — it means the airspace is running normally with no reported delays. That's the correct quiet-state response.
How fresh is it?
Each response carries its observation time and is signed; it surfaces what the FAA reported, not a real-time SLA.