Get flight count statistics (departed, enroute, scheduled) for any airport via FlightAware AeroAPI at $0.20/request.
What it does
This endpoint returns flight count statistics for a specific airport, broken down by departed, enroute, scheduled departures, and scheduled arrivals. It is part of StableTravel's FlightAware airport data suite, which proxies FlightAware AeroAPI through a pay-per-request MPP/x402 micropayment interface. No API keys or subscriptions are required — payment via USDC on Tempo (chainId 4217) serves as authentication.
The endpoint accepts an ICAO or IATA airport code as a path parameter (e.g., KJFK or JFK) and returns a JSON object with numeric counts for each flight category. It costs $0.20 per request (200,000 base units of pathUSD with 6 decimals). The response schema includes `departed`, `enroute`, `scheduled_departures`, and `scheduled_arrivals` fields, all numeric. This is useful for getting a quick operational snapshot of airport activity without pulling full flight lists.
StableTravel is built by Merit Systems and provides over 60 travel-related endpoints spanning Amadeus GDS (flights, hotels, activities, transfers), FlightAware AeroAPI (real-time tracking, airport info, weather, history, disruptions), and Google Flights (price comparison). All endpoints use the same MPP payment protocol and are documented via a full OpenAPI 3.1 spec at /openapi.json.
Capabilities
Use cases
- —Get a quick operational snapshot of how many flights are departed, enroute, or scheduled at an airport
- —Monitor airport congestion levels for travel planning agents
- —Feed airport activity data into dashboards or disruption-detection workflows
- —Compare traffic volumes across airports for logistics or scheduling decisions
Fit
Best for
- —AI travel agents needing a lightweight airport activity check before recommending flights
- —Operations dashboards that need current airport flight volume without full flight lists
- —Autonomous agents that pay per call with no API key setup
Not for
- —Getting detailed individual flight information (use the flights endpoints instead)
- —Historical airport traffic analysis (use the history endpoints)
- —Free or bulk data access — every call costs $0.20
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/airports/KJFK/flights/counts"Example
Response
{
"enroute": 87,
"departed": 142,
"scheduled_arrivals": 198,
"scheduled_departures": 203
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed response types, clear pricing in x-payment-info, live 402 MPP challenge captured, extensive documentation in the guidance field, and well-structured endpoint. Only minor gap is no real example response data from an actual call.
Citations
- —Endpoint costs $0.20 per request (amount 200000 in pathUSD with 6 decimals on Tempo chainId 4217)https://stabletravel.dev/openapi.json
- —Response includes departed, enroute, scheduled_departures, and scheduled_arrivals numeric fieldshttps://stabletravel.dev/openapi.json
- —No API keys needed; payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev
- —Part of StableTravel by Merit Systems, providing pay-per-request access to Amadeus and FlightAware datahttps://stabletravel.dev
- —MPP challenge confirmed live with 402 response and method=tempo, intent=chargehttps://stabletravel.dev/api/flightaware/airports/:id/flights/counts