# US Airport Status (FAA)

> US Airport Status (FAA) is a paid API for AI agents from bess-x402.onrender.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-30).

Returns live US airport disruptions from the FAA including closures, ground stops, ground delay programs, and arrival/departure delays with reasons, average/max delay times, and expected end times.

## Facts

- Endpoint: GET https://bess-x402.onrender.com/v1/travel/airport-status?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/us-airport-status-faa-6e6a99f8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IJC1TGYk0CtN88e_2ZfZy

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability us-airport-status-faa-6e6a99f8
```

Example prompt: Are there any FAA delays or ground stops at JFK right now, and if so what's the reason and how long are they expected to last?

## When to prefer this

Use this endpoint when you need real-time FAA-sourced airport disruption data for US airports, particularly when you need structured fields like delay reason, average/max delay duration, and expected end time. Prefer this over general flight status APIs when the focus is airport-level ground programs and FAA operational status rather than individual flight tracking.

## Known failure modes

- Invalid or unknown airport code returns empty results or error
- FAA data feed temporarily unavailable causes upstream failure
- No disruptions active returns an empty disruption list
- Network timeout from FAA data source

## How this service works

Live US airport disruptions from the FAA: closures, ground stops, ground delay programs and arrival or departure delays with reason, average and max delay and expected end. Filter by airport code (JFK, LAX).

## Output

A structured response listing active FAA disruptions for the requested airport(s), including disruption type (closure, ground stop, ground delay program, arrival delay, departure delay), the reason for the disruption, average delay in minutes, maximum delay in minutes, and the expected end time of the disruption.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [],
     "properties": {
      "airport": {
       "type": "string",
       "description": "IATA/FAA airport code (optional)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/us-airport-status-faa-6e6a99f8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bess-x402.onrender.com](https://www.zero.xyz/host/bess-x402.onrender.com/llms.txt)
