How VoyagerX sources fares, and what each number is allowed to claim.

Fare records come from the Travelpayouts Aviasales fare-data API. It is important to be precise about what that is: it returns lowest fares that the provider has already recorded for a route and date. It is not a live availability search against airline inventory, and VoyagerX does not describe it as one.

The practical consequence is worth stating plainly, because it shapes what you should expect: for a popular route on a near date the provider usually has a recent record, and for a thin route or a far-out date it often has none. When it has none, VoyagerX shows no number at all. It never manufactures one to fill the gap.

Editorial content — route timing, airport notes, seasonal patterns, booking-window guidance — is written and reviewed by a person, not generated. That is what makes a route page eligible to be indexed: no editorial, no place in the sitemap. Corridors without reviewed editorial still render a page, because a traveller who searches for one deserves better than a 404, but such a page states only looked-up or calculated facts — airports, distance, DGCA traffic, the last dated fare — and carries no author and no advice. The AI assistant on the site helps with planning questions and is explicitly barred from stating fares. No model writes route pages.

• Daily fare refresh, 08:30 India time. A scheduled job re-reads the route board from the provider and stores what it finds. It is scheduled as 03:00 UTC; Vercel evaluates cron schedules in UTC, which is 08:30 IST.
• Route traffic, when no fare is held. When the fare provider holds no record for a corridor, VoyagerX says so — and, for Indian domestic routes, cites how many passengers actually flew it. That figure is monthly city-pair traffic published by the Directorate General of Civil Aviation (DGCA), Ministry of Civil Aviation, India, used under the Open Database License (ODbL). It is traffic, not a schedule: it shows a route was flown in the stated month, lags by roughly three months, and never asserts that a flight operates on your date.
• Route board pages regenerate every 5 minutes. The homepage and the main fare board rebuild on a five-minute window, so a stored reading reaches you quickly.
• Secondary boards regenerate every 15 minutes. The themed landing boards run on a slower window because their data is the same set.
• Search results are fetched per request. A search on the results page returns the provider’s answer, or a stored answer for that exact route, date and party up to 90 minutes old, labelled with its own age. It never serves a cached board figure in place of a search.

• Invent, round up, or interpolate a fare that no provider recorded.
• Present a guide estimate as a live or confirmed price.
• Add a VoyagerX markup or booking fee — you pay the partner's own price.
• Rank partners by how much commission they pay.
• Claim seat availability, refund outcomes, or visa decisions as fact.
• Store the card details or passenger data used at the partner's checkout.

VoyagerX is free to use and earns affiliate commission when a visitor books through a partner link. That commission is paid by the partner out of their own margin — the price you pay is the partner's price, and VoyagerX adds nothing to it.

Commission does not influence what you see. Routes are ordered by fare and relevance, partner links exist to complete a search you already started, and the add-on services on route pages are chosen for relevance to that destination. Where a link is an affiliate link, the page says so.