Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / AI/ML / Amadeus / Flight Delay Prediction
Flight Delay Prediction logo

Amadeus Flight Delay Prediction

Browse all Amadeus APIs
✓ Official Vendor SpecAI/MLMl Inferenceoauth21 EndpointsREST

For Agents

Estimate the probability a scheduled flight will be delayed by 30, 60, or 120+ minutes so an agent can warn travellers, adjust connection planning, or trigger proactive rebooking.

Use for: Predict the probability my flight will be delayed, I want to know how likely flight LH441 is to be late tomorrow, Score this upcoming flight's on-time performance, Check whether the first leg of my connection is at risk of delay

Not supported: Does not return live flight status, actual delay minutes, or rebooking options — use only to estimate delay-segment probabilities for a scheduled flight.

The Amadeus Flight Delay Prediction API estimates the probability that a given scheduled flight will be delayed and assigns it to one of four delay segments — under 30 minutes, 30 to 60, 60 to 120, or over 120 minutes. The single GET endpoint takes the carrier code, flight number, scheduled departure date and time, origin, destination, duration, and aircraft code, and returns probability scores per segment. Travel apps use it to set traveller expectations, suggest tighter or looser connection times, and prioritise rebooking outreach.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Flight Delay Prediction to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flight Delay Prediction, 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Flight Delay Prediction API.

Estimate probability of delay across four segments (under 30 min, 30-60, 60-120, 120+) for a given scheduled flight

Score upcoming flights in a traveller's itinerary by likely on-time performance

Flag connecting itineraries with high delay probability on the first leg

Trigger proactive traveller communications when a high-delay-probability flight is approaching

Compare expected reliability across alternative carriers on the same route

Use Cases

Patterns agents use Flight Delay Prediction API for, with concrete tasks.

★ Proactive Delay Notifications

Travel apps run a daily job over upcoming bookings, call /travel/predictions/flight-delay for each segment, and email or push-notify travellers whose flight has a high probability of falling into the 60-120 or 120+ delay band. This gives passengers time to leave for the airport later or arrange alternative ground transport without the integrator needing real-time operational data feeds.

For each booking departing in the next 24 hours, call /travel/predictions/flight-delay and send a notification when the combined probability for the 60-120 or 120+ band exceeds 25 percent.

Tighter Connection Risk Scoring

Self-service booking flows score the first leg of any connecting itinerary with the delay endpoint and surface a warning when the layover is short relative to the predicted delay range. The scoring takes a few hundred milliseconds per leg and can be cached for an itinerary's lifetime, so the impact on checkout latency is minimal.

Given a two-leg itinerary with a 50-minute layover, score the first leg's delay probability and return a warning if the 30-60 or 60-120 band combined exceeds 30 percent.

Carrier Comparison on a Route

Corporate travel managers compare expected reliability of competing carriers on the same city pair by calling the prediction endpoint for representative future flights from each carrier. Aggregated over a week of departures, the resulting probabilities feed a simple reliability score used in supplier negotiations.

Call the delay-prediction endpoint for one representative flight per carrier on JFK-LHR for the next 7 days and rank carriers by expected probability of an under-30-minute delay.

Agent-Driven Itinerary Risk Check via Jentic

An AI travel concierge calls Flight Delay Prediction through Jentic for each leg of a customer's upcoming trip and includes the delay risk in the daily briefing. Jentic resolves OAuth and parameter shaping, so the agent only describes the intent and supplies flight metadata.

Call jentic.search('predict Amadeus flight delay'), load the operation, and execute it with carrierCode, flightNumber, scheduledDepartureDate, scheduledDepartureTime, departureAirportCode, arrivalAirportCode, aircraftCode, and duration to return per-segment probabilities.

Key Endpoints

1 endpoints — the amadeus flight delay prediction api estimates the probability that a given scheduled flight will be delayed and assigns it to one of four delay segments — under 30 minutes, 30 to 60, 60 to 120, or over 120 minutes.

METHOD

PATH

DESCRIPTION

GET

/travel/predictions/flight-delay

Predict delay segment probabilities for a scheduled flight

GET

/travel/predictions/flight-delay

Predict delay segment probabilities for a scheduled flight

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential management

Credential isolation

Amadeus client_id and client_secret are stored encrypted in the Jentic vault. Jentic exchanges them for a short-lived bearer token via the client_credentials flow and refreshes it automatically before each delay-prediction call.

Intent-based discovery

Intent-based discovery

Agents search Jentic by intent ('predict an Amadeus flight delay') and Jentic returns the /travel/predictions/flight-delay operation with the eight required query parameters described in the input schema.

Time to first call

Time to first call

Direct Amadeus integration: 1 day for OAuth and parameter wiring. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

On-Demand Flight Status

→

Returns the live operational status of a scheduled flight, complementing the predictive score.

Use when the flight is within 24-48 hours and live status is more useful than a probability.

Alternative

Airport On-Time Performance

→

Predicts on-time performance at an airport level rather than a specific flight.

Use when the question is about a hub's reliability rather than a specific carrier and flight number.

Complementary

Flight Choice Prediction

→

Scores offers by likelihood the traveller will pick them; pair with delay risk to surface reliable, attractive options.

Use together when the agent should both rank offers and warn about reliability.

Alternative

Trip Purpose Prediction

→

Different prediction model focused on whether a trip is business or leisure rather than delay risk.

Use when segmenting travellers by purpose rather than scoring operational risk.

FAQs

Specific to using Flight Delay Prediction API through Jentic.

What authentication does the Flight Delay Prediction API use?

Amadeus Self-Service OAuth 2.0 client_credentials. Exchange client_id and client_secret at https://api.amadeus.com/v1/security/oauth2/token for a bearer token and pass it in the Authorization header. Through Jentic, the credentials are kept in the encrypted vault and the bearer token is rotated automatically before each prediction call.

Which fields do I have to send to get a prediction?

All eight query parameters are required: originLocationCode, destinationLocationCode, departureDate, departureTime, arrivalDate, arrivalTime, aircraftCode, carrierCode, flightNumber, and duration. Missing any of them returns a 400 from /travel/predictions/flight-delay.

What are the rate limits for the Flight Delay Prediction API?

Amadeus Self-Service Test environment caps prediction endpoints at 10 transactions per second per API key with a fixed monthly quota; Production limits scale with your Self-Service plan tier. Bearer tokens expire after roughly 30 minutes and must be refreshed.

How do I score a flight's delay risk through Jentic?

Run pip install jentic, then call jentic.search('predict Amadeus flight delay'), load the operation, and execute it with the eight required parameters. Jentic handles the OAuth exchange and calls /travel/predictions/flight-delay, returning the delay-segment probabilities.

Does the API tell me the actual delay in minutes?

No. It returns a probability per segment (under 30 min, 30-60, 60-120, 120+). To translate into an expected value, multiply each midpoint by its probability and sum, but treat the output as a risk band rather than a precise prediction.

Is the Flight Delay Prediction API free?

The Test environment is free with limited monthly quota. Production access is metered per transaction under an Amadeus Self-Service plan; pricing is published on the Amadeus for Developers portal.

GET STARTED

Start building with Flight Delay Prediction API

Explore with Jentic
View OpenAPI Document