For Agents
Look up airport details by IATA or ICAO code, search airports by name, calculate distances, find the nearest airport to coordinates, and compare countries. Airport reference data, not flight schedules.
Use for: I need to look up an airport by its IATA code, Find the nearest airport to a latitude and longitude, Get the distance between two airports, Search for airports by name
Not supported: Does not handle flight schedules, bookings, or live flight tracking. Use for airport reference data, distance, and nearest-airport lookups only.
The SITA Aero Airport API serves airport reference data for IATA and ICAO codes, including full airport metadata, name search, and spatial lookups. It returns an airport by code, searches airports by name or partial code, calculates the distance between two airports, finds the nearest airport to a set of coordinates, and checks whether two airports sit in the same country. It covers airport reference data rather than flights, schedules, or bookings.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SITA Aero Airport API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
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%2Fdeveloper.aero%2Fdeveloper-aero" | 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%2Fdeveloper.aero%2Fdeveloper-aero" | 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.
What an agent can do with SITA Aero Airport API.
Look up airport details by IATA or ICAO code
Search airports by name or partial code
Calculate the distance between two airports
Find the nearest airport to a set of coordinates
Check whether two airports are in the same country
Retrieve the full list of airports with their metadata
Patterns agents use SITA Aero Airport API for, with concrete tasks.
★ Agent Airport Lookups
An AI agent connected through Jentic resolves an airport mentioned in a request into structured data by looking it up by IATA or ICAO code, or searching by name when only a partial is given. This gives the agent a reliable code-to-metadata step before it reasons about routes or itineraries.
Look up an airport by its IATA code and return its name, city, and country
Nearest-Airport Routing
A travel or logistics workflow finds the closest airport to a traveller's coordinates so it can suggest a departure point. The nearest-airport lookup takes a latitude and longitude and returns the matching airport, letting the workflow turn a raw location into an actionable airport.
Find the nearest airport to a given latitude and longitude and report its code and distance
Airport Distance Checks
A pricing or planning tool calculates the distance between two airports and checks whether they are in the same country to inform routing and fare logic. Both the distance and same-country checks come from the same airport reference source, so results stay consistent.
Calculate the distance between two airports by code and check whether they are in the same country
6 endpoints — the sita aero airport api serves airport reference data for iata and icao codes, including full airport metadata, name search, and spatial lookups.
METHOD
PATH
DESCRIPTION
/airports
Get all airports
/airports/{airportCode}
Get airport by code
/airports/match/{airportNamePartial}
Search airports by name or code
/airports/distance/{airport1}/{airport2}
Distance between two airports
/airports/nearest/{latitude}/{longitude}
Find the nearest airport to coordinates
/airports/samecountry/{airport1}/{airport2}
Check if two airports are in the same country
/airports
Get all airports
/airports/{airportCode}
Get airport by code
/airports/match/{airportNamePartial}
Search airports by name or code
/airports/distance/{airport1}/{airport2}
Distance between two airports
/airports/nearest/{latitude}/{longitude}
Find the nearest airport to coordinates
/airports/samecountry/{airport1}/{airport2}
Check if two airports are in the same country
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SITA Aero Airport API by hand means running the OAuth2 client-credentials flow to mint a token, refreshing it when it expires, and formatting codes and coordinates into each path. Through Jentic you install once, import the SITA Aero Airport API from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
Every SITA Aero Airport operation is a read-only lookup, and airport codes and coordinates travel in the URL path, so a rule bounds which lookups your agent may call. Pick the ones it needs, such as airport-by-code and nearest-airport search, and leave the rest out.
Credential isolation
Your SITA Aero OAuth2 client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find the nearest airport' or 'airport by IATA code', and Jentic returns the matching SITA Aero Airport operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using SITA Aero Airport API through Jentic.
What authentication does the SITA Aero Airport API use?
The SITA Aero Airport API authenticates with OAuth2 using the client-credentials flow per its OpenAPI spec, exchanging your client credentials for a bearer token at SITA's token endpoint. Through Jentic the credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never reach the agent's context.
Can I find the nearest airport to coordinates with the SITA Aero Airport API?
Yes. The nearest-airport lookup takes a latitude and longitude and returns the closest airport. You can also calculate the distance between two airports by code and check whether two airports are in the same country.
Can I limit what my agent is allowed to do with the SITA Aero Airport API?
Yes. Every operation is a read-only airport lookup, so write a rule that allows only the ones your agent needs, such as airport-by-code and nearest-airport search, and leave the distance or same-country checks out until you want them. Every call the agent makes is logged.
What are the rate limits for the SITA Aero Airport API?
The OpenAPI spec does not state rate limits for the SITA Aero Airport API. Check the SITA developer portal for the request limits that apply to your application and plan.
How do I look up an airport with the SITA Aero Airport API through Jentic?
Search Jentic for 'airport by IATA code' and it returns the airport-by-code operation with its input schema; your agent supplies the code and reads back the airport's metadata. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a SITA Aero Airport MCP server?
You don't need an MCP server to give your agent the SITA Aero Airport API. Jentic connects it directly from the API Directory: import it, store your client credentials once, and your agent calls the lookup and distance operations with scoping and credential isolation applied.
GET STARTED