Flight disruption stats (delays, cancellations) by airline, origin, or destination via FlightAware — $0.01/request.
What it does
This endpoint returns flight disruption counts (delays, cancellations, totals, and disruption scores) aggregated by entity type. The `entity_type` path parameter accepts `airline`, `origin`, or `destination`, letting you query which airlines or airports have the most disruptions. Results can be filtered by time period (today, yesterday, last 3/7/14/30 days) and by a specific entity ID filter. The response includes a paginated array of entities with their delay count, cancellation count, total flights, and a disruption score.
This is one endpoint within the StableTravel platform, which wraps FlightAware AeroAPI data behind pay-per-request micropayments. The price is $0.01 per call, paid via MPP (Tempo method on chain 4217) or x402 using USDC. No API keys or subscriptions are required — payment serves as authentication. Use `npx agentcash fetch` for automatic payment handling.
A companion endpoint at `/api/flightaware/disruption-counts/{entity_type}/{id}` returns disruption stats for a single specific entity (e.g., a particular airline code or airport code) at the same $0.01 price point. Both endpoints support cursor-based pagination via `max_pages` and `cursor` query parameters.
Capabilities
Use cases
- —Rank airlines by delay and cancellation rates over the past week to inform booking decisions
- —Monitor origin/destination airport disruption scores to alert travelers of problematic hubs
- —Build dashboards showing daily disruption trends across airlines
- —Compare airport reliability for route planning by an autonomous travel agent
- —Feed disruption data into risk models for travel insurance or operations planning
Fit
Best for
- —AI travel agents that need real-time disruption intelligence for routing decisions
- —Operations teams monitoring airline and airport performance
- —Data analysts building flight reliability dashboards
Not for
- —Tracking individual live flight positions (use the flights/track endpoints instead)
- —Booking flights or hotels (use the Amadeus-backed endpoints on StableTravel)
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/disruption-counts/airline?time_period=last7days"Example
Response
{
"links": {
"next": null
},
"entities": [
{
"name": "United Air Lines Inc.",
"score": 8.6,
"total": 4200,
"delays": 342,
"entity_id": "UAL",
"entity_type": "airline",
"cancellations": 18
},
{
"name": "American Airlines Inc.",
"score": 7.9,
"total": 3800,
"delays": 290,
"entity_id": "AAL",
"entity_type": "airline",
"cancellations": 12
}
],
"num_pages": 1
}Endpoint
Quality
Full OpenAPI 3.1 schema with response structure, query parameters, clear pricing ($0.01 USD), and live 402 MPP challenge captured. Docs are comprehensive. Minor deduction because no real example response data was captured from a live call — the example response is inferred from the schema.
Warnings
- —Example response is inferred from the OpenAPI schema, not captured from a live call.
- —The path parameter :entity_type must be one of: airline, origin, destination — this is documented in guidance but not enforced in the OpenAPI path schema itself.
Citations
- —Price is $0.01 per request for disruption-counts/{entity_type}https://stabletravel.dev/openapi.json
- —entity_type accepts airline, origin, or destination; time_period supports today, yesterday, last3days, last7days, last14days, last30dayshttps://stabletravel.dev/openapi.json
- —Payment via MPP (Tempo method) or x402 with USDC, no API keys neededhttps://stabletravel.dev
- —Endpoint is live, returning 402 MPP challenge with method=tempo, intent=chargehttps://stabletravel.dev/api/flightaware/disruption-counts/:entity_type
- —Part of StableTravel platform wrapping FlightAware AeroAPIhttps://stabletravel.dev/docs