Install Jentic One Beta

Connect the Cirium FlightStats FIDS API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cirium FlightStats FIDS 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%2Fcirium.io%2Fcirium-fids" | sh

Step 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%2Fcirium.io%2Fcirium-fids" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Cirium FlightStats FIDS API.

Retrieve real-time arrivals for a specific airport by IATA or ICAO code

Retrieve real-time departures for a specific airport in JSON or XML format

Filter the FIDS feed by airport code path parameter for terminal-board displays

Authenticate using appId and appKey via either query parameters or HTTP headers

GET STARTED

Start building with Cirium FlightStats FIDS API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cirium FlightStats FIDS API for, with concrete tasks.

★ Powering an Airport Information Display

Airports and lounges run digital screens showing live arrivals and departures. The Cirium FIDS API returns the structured feed that drives those boards, by airport code and format, refreshed at the cadence the integrator polls. This replaces brittle scraping with a contract-backed feed used across hundreds of FIDS deployments.

GET /flex/fids/rest/v1/json/LHR/arrivals with appId and appKey and render the next 20 arrivals on the lounge screen.

Travel App Flight Status Page

Consumer travel apps embed an airport-board view inside their itinerary screen. Calling the departures endpoint for the user's home airport gives the app a curated set of flights for that day, including scheduled and actual times, gate, and status, so a frequent flyer can monitor their next departure without leaving the app.

GET /flex/fids/rest/v1/json/SFO/departures and surface the user's flight UA123 with current gate and status.

Operations Alerting on Delays

An airline ground-ops team can poll the arrivals endpoint for their hub on a fixed interval to detect flights that have slipped from on-time to delayed, then trigger an alert into Slack or PagerDuty. With only two endpoints to manage, the integration is light enough to run from a small scheduled job.

Every 5 minutes, GET /flex/fids/rest/v1/json/ORD/arrivals and post a delayed-flight summary into the ops channel.

AI Agent Travel Assistant

An AI travel assistant invoked through Jentic can take a user's airport code and return a short narrative summary of arrivals or departures. Jentic isolates the appId and appKey in your Jentic One instance, so the agent never sees the raw credential, and the search-by-intent flow surfaces the right FIDS endpoint without the agent reading Cirium docs.

Search Jentic for 'get airport arrivals from Cirium', load GET /flex/fids/rest/v1/{format}/{airport}/arrivals, and return a one-paragraph summary of LHR arrivals.

Key Endpoints

2 endpoints — the cirium flightstats fids api powers airport flight information display systems by returning real-time arrivals and departures for a given airport.

METHOD

PATH

DESCRIPTION

GET

/flex/fids/rest/v1/{format}/{airport}/arrivals

Real-time arrivals for an airport

GET

/flex/fids/rest/v1/{format}/{airport}/departures

Real-time departures for an airport

GET

/flex/fids/rest/v1/{format}/{airport}/arrivals

Real-time arrivals for an airport

GET

/flex/fids/rest/v1/{format}/{airport}/departures

Real-time departures for an airport

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Cirium FlightStats FIDS API by hand means managing its API key and formatting per-airport arrivals and departures requests against the FlightStats host yourself. Through Jentic you install once, import the Cirium FlightStats FIDS API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

This API is read-only and puts the airport code in the URL path (/{airport}/arrivals), so scope the agent to the two operations it needs: fetching arrivals and departures boards. You choose the operations it may call, so it can be limited to departures alone if that is all it needs.

Credential isolation

Your Cirium API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get airport arrivals' or 'get a departures board', and Jentic returns the matching Cirium operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cirium FlightStats FIDS API through Jentic.

What authentication does the Cirium FlightStats FIDS API use?

The FIDS API uses an appId and appKey credential pair. They can be supplied as query parameters (appId, appKey) or as HTTP headers with the same names. Through Jentic, both values are stored encrypted in your Jentic One instance and never enter the agent's prompt.

Can I get both arrivals and departures from one call?

No - the FIDS API uses two separate endpoints. Call GET /flex/fids/rest/v1/{format}/{airport}/arrivals for arrivals and GET /flex/fids/rest/v1/{format}/{airport}/departures for departures. An integration that needs both should call them in parallel.

What are the rate limits for the FIDS API?

Rate limits are not defined in the OpenAPI spec; they are governed by your Cirium FlightStats subscription tier. Coordinate polling frequency with your account agreement and let Jentic surface 429 responses if the limit is exceeded.

How do I fetch an airport board through Jentic?

Run pip install jentic, then search Jentic for 'get airport arrivals from Cirium'. Jentic returns the GET /flex/fids/rest/v1/{format}/{airport}/arrivals operation. Supply format=json and airport=LHR and execute. Get started with Jentic One, the self-hosted execution layer.

Which response formats does the FIDS API support?

The format path parameter accepts json or xml. JSON is the typical choice for modern integrations; XML is supported for legacy signage systems.

Can I filter by terminal or airline?

The two FIDS endpoints scope by airport code only. To filter by airline or terminal, post-process the response client-side, or look at other Cirium FlightStats APIs that expose schedule and operational detail.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use. This API is read-only and has just two operations, fetching the arrivals board and the departures board by airport code, so you can grant your agent both or restrict it to departures alone if that is all it needs. The appId and appKey stay under your control and are injected only for the calls you have allowed.

Cirium FlightStats FIDS API

Name: Cirium FlightStats FIDS API
Brand: Cirium FlightStats FIDS API
Availability: InStock

Browse all Cirium APIs

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey2 EndpointsREST

For Agents

Fetch real-time arrival and departure boards for any airport from Cirium FlightStats with a simple appId and appKey API-key pair. Two endpoints power FIDS-style screens, travel apps, and flight-status agents.

Use for: I need to show today's arrivals at LHR, Get the departures board for JFK, List all arriving flights at SFO right now, Retrieve scheduled departures for a specific airport in JSON

Not supported: Does not handle ticket booking, fare pricing, or airline schedule changes - use for real-time airport arrivals and departures boards only.

The Cirium FlightStats FIDS API powers airport flight information display systems by returning real-time arrivals and departures for a given airport. The API exposes two endpoints under https://api.flightstats.com - /flex/fids/rest/v1/{format}/{airport}/arrivals and /flex/fids/rest/v1/{format}/{airport}/departures - designed to feed terminal screens, mobile apps, and travel-itinerary tools. Authentication uses an appId plus appKey credential pair, supplied either as query parameters or HTTP headers, and the format path parameter selects JSON or XML responses.

Jentic One on Github View OpenAPI Document