MPPtempoquality 0.88

Get route info between two airports via FlightAware AeroAPI, pay-per-request at $0.04.

Price
$0.04 / call
Protocol
mpp
Verified
no
Endpoint
https://stabletravel.dev/api/flightaware/airports/:id/routes/:dest_id

What it does

This endpoint returns route information between two airports, sourced from FlightAware AeroAPI data. It provides historically filed routes including the route string, filed altitude and airspeed ranges, last departure time, and route distance. The two airport codes are supplied as path parameters (`:id` for origin, `:dest_id` for destination). Optional query parameters include `sort_by` (count or last_departure_time), `date_start`, `date_end`, pagination via `max_pages` and `cursor`.

The endpoint is part of the StableTravel platform, which wraps Amadeus GDS and FlightAware AeroAPI behind a single pay-per-request interface. No API keys or subscriptions are required — payment is handled via the MPP protocol (Tempo method, settling in pathUSD on Tempo L2 chain 4217) or x402. The price for this specific endpoint is $0.04 per request. The endpoint is confirmed live, returning a 402 MPP payment challenge as expected.

The response contains a `routes` array where each entry includes `route` (the filed ATC route string), `last_departure_time`, `filed_altitude_max`, `filed_altitude_min`, `filed_airspeed_max`, `filed_airspeed_min`, and `route_distance`. Pagination links and page counts are also included. This is useful for flight planning, route analysis, and understanding common ATC routings between airport pairs.

Capabilities

airport-route-lookupfiled-route-historyatc-route-dataflightaware-aeroapipay-per-requestmpp-paymentx402-paymentpagination

Use cases

  • —Look up commonly filed ATC routes between two airports for flight planning
  • —Analyze historical route filings between an origin and destination
  • —Determine typical filed altitudes and airspeeds for a city pair
  • —Build route comparison tools for dispatchers or pilots
  • —Feed route data into autonomous travel-planning agents

Fit

Best for

  • —Aviation operations teams needing filed route data between airport pairs
  • —AI agents performing flight planning or route analysis
  • —Developers building aviation analytics dashboards

Not for

  • —Booking commercial flights (use the Amadeus flight search/book endpoints instead)
  • —Real-time flight tracking (use the FlightAware flights/track endpoints)

Quick start

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

Example

Response

{
  "links": {
    "next": null
  },
  "routes": [
    {
      "route": "GREKI6 GREKI J80 BETTE J584 KAMMA J134 HIWAY HIIWY2",
      "route_distance": "2145",
      "filed_airspeed_max": 460,
      "filed_airspeed_min": 420,
      "filed_altitude_max": 390,
      "filed_altitude_min": 350,
      "last_departure_time": "2025-06-10T14:30:00Z"
    }
  ],
  "num_pages": 1
}

Endpoint

URLhttps://stabletravel.dev/api/flightaware/airports/:id/routes/:dest_id
Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.88/ 1.00

Full OpenAPI 3.1 schema with response structure, clear pricing ($0.04/request), live 402 MPP challenge confirmed, comprehensive documentation in the guidance field. Slightly below 0.9 because no real example response data was captured from a live call and the response schema items use additionalProperties.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/TRydV2