MPPtempoquality 0.88

Get flights between two airports via FlightAware AeroAPI, pay-per-request at $0.10.

Price
$0.1 / call
Protocol
mpp
Verified
no

What it does

This endpoint returns current flights operating between two specific airports, identified by ICAO or IATA codes in the URL path parameters `:id` (origin) and `:dest_id` (destination). It is part of the StableTravel platform, which wraps FlightAware's AeroAPI behind a pay-per-request micropayment layer. Each call costs $0.10 USD, settled via the MPP protocol using pathUSD on Tempo (chain 4217) or x402 with USDC. No API keys or subscriptions are required — payment serves as authentication.

The response contains an array of flight objects with detailed operational data: FlightAware flight IDs, idents (ICAO/IATA), operator info, origin/destination airport metadata, scheduled/estimated/actual gate and runway times, delays, aircraft type, route distance, filed altitude and airspeed, baggage claim, gate and terminal info, and flight status. Pagination is supported via `cursor` and `max_pages` query parameters. Optional filters include `type`, `connection`, `date_start`, and `date_end`.

This endpoint is useful for monitoring all active and scheduled flights on a specific city pair, analyzing route frequency, or building airport-to-airport dashboards. It sits within a broader StableTravel API suite covering Amadeus-powered flight booking, hotel search, activities, transfers, Google Flights price comparison, and the full FlightAware AeroAPI surface for real-time tracking, history, weather, and disruption data.

Capabilities

airport-to-airport-flightsreal-time-flight-dataflightaware-aeroapiflight-statusflight-delay-infopaginationdate-range-filtermpp-micropaymentx402-paymentno-auth-required

Use cases

  • Monitor all flights currently operating between two airports (e.g., JFK to LAX)
  • Build a dashboard showing flight frequency and delays on a specific route
  • Feed an AI travel agent with real-time route availability data
  • Analyze on-time performance between two airports over a date range
  • Trigger alerts when new flights appear on a watched city pair

Fit

Best for

  • AI travel agents needing real-time airport-pair flight data
  • Aviation analytics dashboards tracking route-level operations
  • Developers who want FlightAware data without managing API keys or subscriptions

Not for

  • Searching for the cheapest bookable fare (use Google Flights or Amadeus endpoints instead)
  • Historical flight data between airports (use the /history/ variant at $0.24/call)
  • Bulk data export of all global flights

Quick start

npx agentcash fetch "https://stabletravel.dev/api/flightaware/airports/KJFK/flights/to/KLAX"

Example

Response

{
  "links": {
    "next": null
  },
  "flights": [
    {
      "ident": "UAL123",
      "origin": {
        "city": "New York",
        "code": "KJFK",
        "name": "John F Kennedy Intl",
        "code_iata": "JFK"
      },
      "status": "En Route",
      "operator": "United Air Lines",
      "ident_iata": "UA123",
      "destination": {
        "city": "Los Angeles",
        "code": "KLAX",
        "name": "Los Angeles Intl",
        "code_iata": "LAX"
      },
      "estimated_in": "2025-07-15T17:30:00Z",
      "fa_flight_id": "UAL123-1718000000-schedule-0001",
      "aircraft_type": "B763",
      "scheduled_out": "2025-07-15T14:00:00Z",
      "route_distance": 2475,
      "progress_percent": 45
    }
  ],
  "num_pages": 1,
  "num_flights": 1
}

Endpoint

Quality

0.88/ 1.00

Full OpenAPI 3.1 schema with detailed response types, clear pricing ($0.10/call), live 402 MPP challenge captured, comprehensive documentation and guidance. Minor deduction because no inline example responses are provided in the spec and the endpoint uses path params that appear as literal placeholders in the OpenAPI paths.

Warnings

  • OpenAPI path uses literal '/id/' and '/dest_id/' rather than proper {id}/{dest_id} path parameter syntax, which may confuse some code generators
  • No example response bodies are included in the OpenAPI spec for this endpoint

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 16:39:52Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access