Flight status lookup by carrier code, flight number, and date via Amadeus — $0.005/request, paid with USDC on Tempo.
What it does
This endpoint returns flight schedule and status information from the Amadeus GDS. You provide an airline IATA carrier code (e.g. AA), a flight number (e.g. 100), and a scheduled departure date (YYYY-MM-DD), and receive status data for that flight. An optional operationalSuffix parameter is also supported.
The endpoint is part of StableTravel, a pay-per-request travel API suite covering flights, hotels, activities, transfers, and real-time flight tracking. StableTravel wraps Amadeus and FlightAware data behind MPP/x402 micropayment protocols — no API keys, no OAuth, no subscriptions. This specific endpoint costs $0.0054 per call, settled in pathUSD on Tempo (chain ID 4217). Payment is handled automatically via the MPP protocol header exchange. The response returns a JSON object with a `data` array containing flight status records, plus optional `dictionaries`, `meta`, and `warnings` fields.
For real-time position tracking, live flight maps, or ATC routing data, StableTravel also offers FlightAware endpoints at different price points. This Amadeus-based status endpoint is best suited for schedule confirmation and basic status checks rather than live GPS tracking.
Capabilities
Use cases
- —Check if a specific flight is on time, delayed, or cancelled before heading to the airport
- —Confirm flight schedule details (departure/arrival times) for a given carrier and date
- —Build travel assistant agents that monitor flight status for booked itineraries
- —Integrate flight status checks into customer notification workflows
- —Validate flight information as part of a booking confirmation pipeline
Fit
Best for
- —AI agents that need quick flight status checks without API key management
- —Travel automation workflows requiring Amadeus schedule data at sub-cent cost
- —Developers building chatbots or assistants that answer 'Is my flight on time?'
Not for
- —Real-time GPS position tracking of in-flight aircraft (use FlightAware endpoints instead)
- —Historical flight performance analytics over large date ranges
- —Bulk batch processing of thousands of flights (per-request pricing adds up)
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flights/status?carrierCode=AA&flightNumber=100&scheduledDepartureDate=2025-06-15"Example
Response
{
"data": [
{
"type": "flight-status",
"status": "Active",
"arrival": {
"iataCode": "LHR",
"scheduledTime": "2025-06-16T06:15:00"
},
"departure": {
"iataCode": "JFK",
"scheduledTime": "2025-06-15T18:00:00"
},
"carrierCode": "AA",
"flightNumber": "100",
"scheduledDepartureDate": "2025-06-15"
}
],
"meta": {
"count": 1
}
}Endpoint
Quality
Full OpenAPI 3.1 schema with parameter definitions, clear pricing in x-payment-info, live 402 MPP challenge captured, and comprehensive guidance docs. Docked slightly because no example response body was provided in the spec (response items are untyped `{}`) and no actual 200 response was captured in the probe.
Warnings
- —Response schema items are untyped (empty `{}`) — actual response structure must be inferred from Amadeus documentation
- —Example response JSON is illustrative and inferred from Amadeus conventions, not captured from a live call
Citations
- —Endpoint costs $0.0054 per request (fixed price in USD)https://stabletravel.dev/openapi.json
- —Payment settles via Tempo method on chain ID 4217 using pathUSDhttps://stabletravel.dev/openapi.json
- —Required parameters: carrierCode, flightNumber, scheduledDepartureDatehttps://stabletravel.dev/openapi.json
- —Part of StableTravel suite covering flights, hotels, activities, transfers, and FlightAware trackinghttps://stabletravel.dev
- —No API keys needed — payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev/openapi.json
- —MPP 402 challenge is live with method=tempo and intent=chargehttps://stabletravel.dev/api/flights/status