> ## Documentation Index
> Fetch the complete documentation index at: https://docs.farelint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Airline coverage

> Your carriers, your routes and a clearly defined data contract.

The current website illustrates Ryanair, easyJet, Wizz Air, TAP Air Portugal, Lufthansa and AEGEAN. These examples do not establish live integrations or airline partnerships.

## Define a coverage request

| Dimension | Example |
| - | - |
| Source airline | Ryanair / FR |
| Airport pair | Porto OPO to Rome FCO |
| Travel horizon | Exact dates or a bounded date window |
| Journey | One way or an exact outbound/return date pair |
| Traveller mix | Adults, child ages and infants |
| Cabin and fare | Cabin plus required baggage or fare-brand fields |
| Market | Point of sale, locale and requested currency |
| Delivery | On demand, recurring API feed or export |

## Before a carrier is enabled

We need to validate source access, permissible use, available fields, collection success, freshness and operating cost. A coverage agreement records supported query shapes and known gaps. Some routes or fields may be unavailable even when a carrier is enabled.

## Source-specific costs

Each enabled source will have a published credit weight before dispatch. A difficult collection may cost more than a standard query. Different source weights use the same workspace credit balance.

[Tell us which airlines you need](https://out-of-cyprus-larnaca.m3k3r1.chatgpt.site/#access).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.