canonical: https://jentic.com/apis/developer.aero/developer-aero # Aero SITA Aero Airport API 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. ## For AI 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. ## Scope Does not handle flight schedules, bookings, or live flight tracking. Use for airport reference data, distance, and nearest-airport lookups only. ## Capabilities - 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 ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Calculate the distance between two airports by code and check whether they are in the same country ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/airports` | Get all airports | | GET | `/airports/{airportCode}` | Get airport by code | | GET | `/airports/match/{airportNamePartial}` | Search airports by name or code | | GET | `/airports/distance/{airport1}/{airport2}` | Distance between two airports | | GET | `/airports/nearest/{latitude}/{longitude}` | Find the nearest airport to coordinates | | GET | `/airports/samecountry/{airport1}/{airport2}` | Check if two airports are in the same country | ## Key resources - **Airports** — Look up airports by code or name and list all airports with metadata - **Spatial lookups** — Distance between airports, nearest airport to coordinates, and same-country checks ## AI readiness 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. - **Score:** 71 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 51 / 100 - Agent Usability: 94 / 100 - Security: 85 / 100 - AI Discoverability: 71 / 100 - **View full report:** https://jentic.com/apis/developer.aero/developer-aero/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Airport Gap API** — Also serves airport data and distances between airports, with SITA Aero adding IATA and ICAO code lookups and nearest-airport search. - **aviationstack API** — Covers live flights and schedules that pair with SITA Aero's airport reference data. - **Amadeus for Developers API** — Provides flight and hotel booking that relies on the airport codes SITA Aero resolves. ## FAQ ### 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.