Install Jentic One Beta

Connect the OAG Flight Info API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OAG Flight Info 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%2Foag.com%2Foag" | 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%2Foag.com%2Foag" | 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 OAG Flight Info API.

Look up real-time flight status and scheduled times for a specific carrier and flight number

Find viable connecting flight options between two airports for a given date

Create flight alerts that notify a webhook on status, gate, or time changes

List active flight alerts for an account to audit which itineraries are being monitored

GET STARTED

Start building with OAG Flight Info API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use OAG Flight Info API for, with concrete tasks.

★ Real-time itinerary status for travel platforms

Keep traveller-facing apps in sync with airline operations by polling GET /flights for each leg of an itinerary or by subscribing to alerts that push updates when status or times change. The OAG Flight Info API exposes scheduled, estimated, and actual times alongside gate and equipment fields, which lets a travel platform display accurate disruption messages without screen-scraping carrier sites. Integration usually takes a couple of days end to end.

Call GET /flights for each leg of a 3-leg itinerary on the day of departure and surface any leg whose status is not 'On Time'

Connection planning for irregular operations

Recover passengers from a misconnect by calling GET /connections between an arrival airport and the original destination to retrieve viable onward flights. The endpoint accepts origin, destination, and time parameters so the agent can rank options by total elapsed time. Operations teams can wire this into chat tools to give agents an immediate set of rebooking candidates.

Call GET /connections from LHR to ATH for a passenger who misconnected at LHR and present the next three viable onward flights

Gate-to-gate alerting for ground operations

Keep ground handling and meet-and-greet teams aligned with operations by creating flight alerts that fire when status, gate, or times shift. POST /alerts subscribes a webhook for a specific flight, GET /alerts and GET /alerts/{alertId} let teams audit active subscriptions, and DELETE /alerts/{alertId} retires expired ones. The pattern reduces the number of standing polls operations teams need to run.

POST /alerts for tomorrow's BA178 with a webhook URL, then call GET /alerts to verify the subscription is active

AI agent integration via Jentic

A travel concierge agent searches Jentic for flight status, loads the GET /flights operation, and answers questions like 'is my passenger's BA flight on time and which gate?'. When a delay is detected the agent calls POST /alerts to subscribe a webhook so it can react to further changes. Jentic supplies validated schemas so the agent can call /flights, /connections, and /alerts without parsing the OAG documentation.

Use Jentic to search 'real-time flight status', load GET /flights, and execute it with carrier=BA flightNumber=178 for today's date

Key Endpoints

6 endpoints — the oag flight info api provides real-time and scheduled flight data for the global commercial aviation network.

METHOD

PATH

DESCRIPTION

GET

/flights

Get real-time and scheduled flight information

GET

/connections

Get connecting flight options between two airports

POST

/alerts

Create a flight alert subscription

GET

/alerts

List active flight alerts

GET

/alerts/{alertId}

Get a specific flight alert

DELETE

/alerts/{alertId}

Delete a flight alert

GET

/flights

Get real-time and scheduled flight information

GET

/connections

Get connecting flight options between two airports

POST

/alerts

Create a flight alert subscription

GET

/alerts

List active flight alerts

GET

/alerts/{alertId}

Get a specific flight alert

DELETE

/alerts/{alertId}

Delete a flight alert

Why Jentic?

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

Setup

Wiring the OAG Flight Info API by hand means managing your subscription key, adding it to the Ocp-Apim-Subscription-Key header on every request, and coding your own retry and rate-limit handling against api.oag.com. Through Jentic you install once, import the OAG Flight Info API from the API Directory, store the key once, and your agent calls it.

Permission scoping

OAG puts the alert id in the URL path (/alerts/{alertId}), so a rule can pin your agent to the alerts and flight operations it needs: it can read flights, look up connections, and read alerts, for example. You choose the operations it may call, so creating alerts with POST /alerts or deleting them with DELETE /alerts/{alertId} is not included unless you add it.

Credential isolation

Your OAG subscription key is stored once, encrypted, by your own Jentic One instance and injected into the Ocp-Apim-Subscription-Key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'real-time flight status' or 'find connecting flights', and Jentic returns the matching OAG operation with its input schema so the agent calls the right endpoint without reading the OAG docs.

FAQs

Specific to using OAG Flight Info API through Jentic.

What authentication does the OAG Flight Info API use?

The API requires an Azure-style subscription key sent in the Ocp-Apim-Subscription-Key header on every call to /flights, /connections, and /alerts. Through Jentic the key is held in the vault (your Jentic One instance) and injected at execution time so it never appears in the agent's prompt context.

Can I track real-time flight status with the OAG Flight Info API?

Yes. GET /flights returns scheduled, estimated, and actual times along with status, gate, and equipment for a specific carrier flight number on a given date. For push updates rather than polling, POST /alerts subscribes a webhook for the same flight.

Can I find connecting flights between two airports with this API?

Yes. GET /connections accepts origin, destination, and time parameters and returns viable onward flights between the two airports. The response is suitable for rebooking flows during irregular operations.

What are the rate limits for the OAG Flight Info API?

The OpenAPI spec does not publish explicit rate limits. OAG controls limits per subscription tier; check your contracted plan or contact OAG support for figures. Through Jentic, the agent loop can pace calls to avoid bursts that exceed your plan.

How do I subscribe to flight alerts through Jentic?

Install the SDK with pip install jentic, search 'create a flight alert', load POST /alerts, and execute it with the carrier flight number, departure date, and webhook URL. To retire alerts the agent calls DELETE /alerts/{alertId} with the ID returned from the original POST.

How do I look up viable connections after a misconnect?

Call GET /connections with the new origin (the misconnect airport), the original destination, and the earliest acceptable departure time. Filter the response on total elapsed time or carrier preference, and present the top options to the operations agent.

Can I limit what my agent is allowed to do with the OAG Flight Info API?

Yes. Because you run Jentic One yourself, your own rules decide which OAG operations and credentials the agent may use. You can pin the agent to read-only work, such as looking up flight status on GET /flights, finding onward options on GET /connections, and reading existing alerts, while withholding write operations. Creating a subscription with POST /alerts or removing one with DELETE /alerts/{alertId} is not available to the agent unless you explicitly add it.

OAG Flight Info API

Name: OAG Flight Info API
Brand: OAG Flight Info API
Availability: InStock

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey6 EndpointsREST

For Agents

Look up real-time and scheduled flight information, find connecting flight options, and subscribe to status alerts for any commercial flight.

Use for: Get the current status and gate of flight BA178 today, Retrieve scheduled departure and arrival times for a specific carrier flight number, Find all connecting flight options from JFK to ATH on a given date, Check whether a flight is delayed and by how many minutes

Not supported: Does not handle ticket booking, fare pricing, or seat selection - use for flight status, connection lookup, and operational alerts only.

The OAG Flight Info API provides real-time and scheduled flight data for the global commercial aviation network. It returns flight statuses, scheduled and actual times, equipment, and airline schedule information, and lets clients subscribe to flight alerts that fire when status or times change. Travel platforms, ground handling teams, and corporate travel programmes use it to keep itineraries and operational dashboards aligned with what is actually happening at airports.

Jentic One on Github View OpenAPI Document

Connect the OAG Flight Info API to your agent

Capabilities

Start building with OAG Flight Info API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

OAG Flight Info API