Find nearby airports by latitude/longitude via Amadeus reference data, $0.005/request over MPP.
What it does
This endpoint is part of StableTravel's Reference Data category. It accepts latitude, longitude, and an optional radius parameter (default 500 km) via GET and returns a list of nearby airports from Amadeus's reference database. Results can be sorted by relevance, distance, or traveler/flight analytics scores, and paginated with page[limit] and page[offset] parameters.
The endpoint costs $0.0054 per request (as indicated by the OpenAPI spec's x-payment-info amount of 0.005400 USD). Payment is handled automatically via the MPP protocol using the Tempo method on chain 4217, settling in pathUSD. No API keys or authentication are required — the micropayment itself serves as auth. The endpoint returned a 402 MPP challenge on probe, confirming it is live.
StableTravel is operated by Merit Systems and wraps Amadeus GDS and FlightAware AeroAPI data behind a pay-per-request facade. The full OpenAPI 3.1 spec is published at /openapi.json and interactive docs are available at /docs. This specific endpoint is useful as a building block for travel agents that need to resolve geographic coordinates to the nearest airports before searching flights or hotels.
Capabilities
Use cases
- —Resolve a user's GPS coordinates to the nearest IATA airport codes before searching flights
- —Build a travel planning agent that automatically selects departure airports based on location
- —Populate airport suggestions in a map-based travel UI
- —Determine which airports serve a given geographic area for logistics or routing
Fit
Best for
- —AI travel agents that need to convert coordinates to airport codes
- —Autonomous trip planners that start from a location rather than a known airport
- —Developers building location-aware flight search workflows
Not for
- —Real-time flight tracking or live flight positions (use FlightAware endpoints instead)
- —Searching or booking flights directly (use /api/flights/search)
- —Looking up airports by name or keyword (use /api/reference/locations)
Quick start
npx agentcash fetch "https://stabletravel.dev/api/reference/airports?latitude=40.7128&longitude=-74.0060"Example
Response
{
"data": [
{
"name": "NEWARK LIBERTY INTL",
"type": "location",
"geoCode": {
"latitude": 40.6925,
"longitude": -74.1687
},
"subType": "AIRPORT",
"distance": {
"unit": "KM",
"value": 14.2
},
"iataCode": "EWR"
}
],
"meta": {
"count": 5
}
}Endpoint
Quality
Full OpenAPI 3.1 schema with parameter definitions, clear pricing in x-payment-info, live 402 MPP challenge confirmed, comprehensive guidance docs. Docked slightly because the response schema for this specific endpoint uses untyped `items: {}` in the data array, and no real example response was captured.
Warnings
- —Response schema data items are untyped (items: {}) — actual Amadeus response structure must be inferred from Amadeus documentation
- —Example response is synthetic based on typical Amadeus reference data shape, not captured from a live call
Citations
- —Endpoint costs $0.0054 per request (amount 0.005400 USD)https://stabletravel.dev/openapi.json
- —Accepts latitude, longitude, radius, page[limit], page[offset], sort parametershttps://stabletravel.dev/openapi.json
- —Payment via MPP protocol using Tempo method on chain 4217, no API keys neededhttps://stabletravel.dev/openapi.json
- —Part of StableTravel operated by Merit Systems, wrapping Amadeus and FlightAware datahttps://stabletravel.dev
- —Endpoint returned live 402 MPP challenge with amount 5400 in pathUSDhttps://stabletravel.dev/api/reference/airports