FlightAware airport info via pay-per-request API — $0.03 per call, no API keys needed.
What it does
This endpoint returns detailed information for a specific airport identified by its ICAO or IATA code. It is part of StableTravel's FlightAware integration, which proxies FlightAware AeroAPI data through a pay-per-request micropayment model. The response includes the airport's name, ICAO/IATA/LID codes, geographic coordinates (latitude, longitude), elevation, city, state, country code, timezone, wiki URL, a link to the airport's flights page, and a list of alternative nearby airports. The endpoint accepts ICAO codes (e.g., KJFK) or IATA codes (e.g., JFK) as the path parameter.
Pricing is $0.03 per request, settled via USDC on Tempo (chainId 4217) using the MPP or x402 micropayment protocol. No API keys, OAuth tokens, or subscriptions are required — payment serves as authentication. The endpoint is live and returns a 402 MPP challenge to unauthenticated callers, confirming it is operational.
This endpoint is one of many in StableTravel's FlightAware airport suite, which also covers delays, weather (METAR/TAF), arrivals, departures, scheduled flights, flight counts, nearby airports, and inter-airport routes. The full OpenAPI 3.1 spec is published at /openapi.json with detailed response schemas for each endpoint.
Capabilities
Use cases
- —Retrieve airport details (name, location, timezone) for travel planning agents
- —Resolve IATA/ICAO codes to full airport metadata for flight booking workflows
- —Get airport coordinates for mapping or distance calculations
- —Find alternative airports near a given airport
- —Enrich flight data with origin/destination airport information
Fit
Best for
- —AI travel agents that need airport metadata on demand
- —Flight tracking applications needing airport reference data
- —Autonomous booking agents that resolve airport codes programmatically
Not for
- —Real-time flight tracking (use the flights endpoints instead)
- —Bulk downloading of all airport data (pagination exists but is expensive at $0.03/call)
- —Free-tier or high-volume airport lookups where cost matters
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/airports/JFK"Example
Response
{
"city": "New York",
"name": "John F Kennedy Intl",
"type": "Airport",
"state": "NY",
"code_lid": "JFK",
"latitude": 40.6398,
"timezone": "America/New_York",
"wiki_url": "https://en.wikipedia.org/wiki/John_F._Kennedy_International_Airport",
"code_iata": "JFK",
"code_icao": "KJFK",
"elevation": 13,
"longitude": -73.7789,
"airport_code": "KJFK",
"alternatives": [
{
"city": "New York",
"name": "LaGuardia",
"airport_code": "KLGA"
}
],
"country_code": "US",
"airport_flights_url": "/airports/KJFK/flights"
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed response types, clear pricing ($0.03/call), live 402 MPP challenge captured, comprehensive documentation including parameter descriptions and response fields. Example response is inferred from schema rather than captured live, which is the only gap.
Warnings
- —Example response is synthesized from the OpenAPI schema, not captured from a live paid call.
- —The path parameter :id is not explicitly documented in the OpenAPI path — the spec uses /api/flightaware/airports/id as a literal path; actual usage requires substituting the airport code.
Citations
- —Endpoint price is $0.03 per requesthttps://stabletravel.dev/openapi.json
- —Payment via USDC on Tempo (chainId 4217) using MPP protocolhttps://stabletravel.dev/openapi.json
- —Response includes airport_code, name, ICAO/IATA/LID codes, coordinates, elevation, timezone, alternativeshttps://stabletravel.dev/openapi.json
- —No API keys needed — payment via x402/MPP serves as authenticationhttps://stabletravel.dev
- —Endpoint is live (402 MPP challenge captured)https://stabletravel.dev/api/flightaware/airports/:id
- —Accepts ICAO or IATA airport code as path parameterhttps://stabletravel.dev/openapi.json