canonical: https://jentic.com/apis/cirium.io/cirium

# Cirium FlightStats FIDS API

The Cirium FlightStats FIDS API returns flight information display board data for an airport, covering scheduled arrivals and departures. It takes an airport code and a response format in the path and returns the flights for that board. Agents can build live arrival and departure displays or answer flight-status questions for a given airport without ingesting a raw aviation feed.

## For AI agents

Retrieve the arrivals or departures flight information display board for an airport from Cirium FlightStats. Returns scheduled flight board data for an agent to present or monitor.

## Scope

Does not handle live aircraft tracking, per-flight status detail, or bookings. Use for airport arrivals and departures board data only.

## Capabilities

- Retrieve the arrivals board for an airport
- Retrieve the departures board for an airport
- Request flight board data in the response format a display needs

## Use cases

### Agent-Powered Flight Board Lookup

An AI agent answers airport questions by retrieving the arrivals or departures board for a requested airport. It reads the flights on the board and reports which are arriving or leaving and when. This gives an agent a direct source of flight information display data without parsing a raw aviation feed.

Example prompt: Retrieve the arrivals and departures boards for a requested airport and report the upcoming flights on each

### Terminal Display Feed

Airport and travel displays pull the arrivals or departures board and render it for travelers. The API returns the board in a requested response format so it can feed a screen directly. This suits a recurring refresh that keeps a display current with scheduled flights.

Example prompt: Fetch the departures board for an airport in the required format and refresh the terminal display with the current flights

### Arrival and Departure Monitoring

An agent watches an airport's boards and surfaces changes such as new arrivals or departures for a travel workflow. It retrieves both boards for the airport and compares them across refreshes. This turns flight board data into a monitored signal rather than a one-off lookup.

Example prompt: Retrieve the arrivals and departures boards for an airport on a schedule and report flights that appeared since the last check

## Key resources

- **Arrivals board** — Scheduled arriving flights for a given airport
- **Departures board** — Scheduled departing flights for a given airport

## Why Jentic

- **Setup:** Wiring the Cirium FlightStats FIDS API by hand means managing an appId and appKey, choosing where to send them, and formatting the airport and response type in the path. Through Jentic you install once, import Cirium from the API Directory, store the keys once, and your agent retrieves airport boards.
- **Permission scoping:** Cirium puts the airport code in the URL path, so a rule can bound your agent to a single airport's boards. The API is read-only, so the agent cannot change anything, and every call it makes is logged.
- **Credential handling:** Your Cirium appId and appKey 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 'airport arrivals board' or 'airport departures', and Jentic returns the matching Cirium operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **aviationstack** — Real-time and historical flight status and schedule data
- **Flightradar24** — Live flight tracking and positional data API
- **Amadeus Flight Status** — On-demand flight status lookups for a specific flight

## FAQ

### What authentication does the Cirium FlightStats FIDS API use?

The Cirium FlightStats FIDS API authenticates with an appId and appKey per its OpenAPI spec, which can be sent as query parameters or as request headers. Through Jentic those values are held encrypted by your own Jentic One instance and attached at call time, so they never reach the agent's context.

### Can I get both arrivals and departures for an airport with this API?

Yes. The API exposes an arrivals board and a departures board, each addressed by the airport code in the path. An agent can retrieve both to present a full picture of an airport's schedule.

### What are the rate limits for the Cirium FlightStats FIDS API?

The OpenAPI spec does not specify rate limits. Check the Cirium developer documentation at https://developer.flightstats.com for current limits and usage guidance.

### Can I limit what my agent is allowed to do with the Cirium FlightStats FIDS API?

Yes. Because the airport code sits in the URL path, a rule can bound your agent to arrivals and departures for a single airport, and the API is read-only so it cannot change any data. Every call the agent makes is logged.

### How do I read airport flight boards through Jentic?

Search Jentic for 'airport arrivals board', add the Cirium FlightStats FIDS API from the directory, and store your keys once. Your agent then retrieves the arrivals or departures board for an airport. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Cirium MCP server?

You don't need an MCP server to give your agent the Cirium FlightStats FIDS API. Jentic connects it directly from the API Directory: import it, store your keys once, and your agent reads airport flight boards. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.