# StableTravel FlightAware Historical Flights by Operator

> StableTravel FlightAware Historical Flights by Operator is a paid API for AI agents from StableTravel at stabletravel.dev, paid per call via MPP, $0.04/call, status unknown (last checked 2026-09-14).

Retrieves historical flight records for a specific airline or operator within a geographic bounding box

## Facts

- Endpoint: GET https://stabletravel.dev/api/flightaware/history/operators/:id/flights
- Price: $0.04/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Provider: StableTravel
- Docs: https://stabletravel.dev
- Website: https://stabletravel.dev
- Tags: amadeus, flightaware, flights, hotels, activities, transfers, travel, data, web
- Canonical page: https://www.zero.xyz/c/stabletravel-flights-8bf42ad6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XgMmJk2AicplAUW_9Mt6l

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability stabletravel-flights-8bf42ad6
```

Example prompt: Pull the historical flights for operator UAL within the bounding box from 49.0° N to 25.0° N latitude and -125.0° W to -66.0° E longitude, up to 100 results.

## When to prefer this

Use this endpoint when you need historical (past) flight data for a specific airline or operator filtered by geographic region. Prefer this over the 'Get all flights at an airport' endpoint when you need operator-specific history across a region rather than all flights at a single airport. Ideal for analytics, route analysis, or auditing past operator activity in a geographic area.

## Known failure modes

- Invalid or unknown operator ID returns an error or empty result set
- Invalid bounding box coordinates (e.g. north < south) cause a validation error
- Bounding box too large may return truncated results or timeout
- No historical flights found for operator in the given region returns empty array
- Missing required bounding box parameters returns a 400-level error

## How this service works

Get historical flights by operator

## Output

A list of historical flight records for the specified operator that occurred within the defined geographic bounding box, including details such as flight identifiers, routes, and timing data — up to the specified maximum number of results.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "north",
  "west",
  "south",
  "east"
 ],
 "properties": {
  "max": {
   "type": "number",
   "description": "Maximum number of results (default 50)"
  },
  "east": {
   "type": "number",
   "description": "Eastern longitude boundary"
  },
  "west": {
   "type": "number",
   "description": "Western longitude boundary"
  },
  "north": {
   "type": "number",
   "description": "Northern latitude boundary"
  },
  "south": {
   "type": "number",
   "description": "Southern latitude boundary"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stabletravel-flights-8bf42ad6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stabletravel.dev](https://www.zero.xyz/host/stabletravel.dev/llms.txt)