Jentic publishes the only available OpenAPI specification for AviationData.Systems Airports API V1, keeping it validated and agent-ready. The Airports API exposes a global airport reference dataset with lookup by IATA code, fuzzy name autocomplete, nearest-airport search by latitude and longitude, and country-level airport listings. It is intended for travel apps, flight tooling, and any workflow that needs to resolve airport codes, names, and coordinates without maintaining its own dataset.
The AviationData.Systems Airports API looks up airport and country reference data over REST. It finds airports by IATA code, by name, or by autocomplete prefix, returns the airports nearest to a set of coordinates, and lists countries and their codes. The specification declares HTTP basic authentication, though these lookup endpoints require no credential.
The AviationData.Systems Airports API resolves airport reference data from a global airport dataset. It looks up an airport by its IATA code, matches airports by name, autocompletes partial airport-name input, and returns the airports nearest to a given latitude and longitude pair with a caller-controlled result count. It also resolves a country by its country code and returns the full country list, so an agent can map an airport back to the country that operates it. The responses carry reference attributes such as airport names, codes, and location, making the API a lookup layer for airport and country identifiers rather than a live flight-tracking or booking service.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faviationdata.systems" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faviationdata.systems" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.