Free tool
Free Flight Price Checker
A fare on its own is just a number. This checker returns the live fare with Google's price band and verdict, so you know whether to book or to wait.
JFK → CUN · 2027-01-01
captured run · 2026-08-26Google's price band for this route & dates. Cheapest live fare: $177
How it works
Three steps, one field that matters
1
Enter a route and date
Airport codes and a departure date, the same inputs the API takes.
2
We run a real search
A live scan of Google Flights through the FlightPowers API, on our key, at request time. No cache, no stale fares.
3
Read the verdict
The gauge places the fare on Google’s historical band; the badge shows Google’s own low | typical | high call.
Who uses it
Built for the question everyone actually asks
Not "what does it cost" but "should I book it now?"
Travellers with a quote
You have a price from a booking site. Check it against Google's band before paying. Below the low end means book, above the high end means keep looking.
Developers evaluating the API
This tool IS the API: same endpoint, same fields, our key. The free RapidAPI tier is a 10-request hard cap, so evaluate here where runs are free.
Deal hunters
A "deal" is only a deal relative to the usual price. The verdict is computed from the route's own history, not from a marketing banner.
Scale it
Checking hundreds of routes? That's what the API is for
This page runs one check at a time. Your code doesn't have to.
Parallel date scans
150–500 requests/minute by tier: a whole month of dates in one burst, not a serial loop.
Alerts on the verdict
Poll a route and fire when the verdict flips to low. No price-history database needed.
Every result bookable
A working buy_link into Google Flights on every row.
Questions, answered plainly
- Is this checker really free?
- Yes. No account, no email. Each check runs a real search against live Google Flights data on our own API key, so live checks are capped per visitor per day and repeated queries are served from a short-lived cache. The page shows a captured example until you run one.
- What do “low”, “typical”, and “high” mean?
- They are Google’s own verdict comparing the current fare to the historical price range for that route and date window. “Low” means the fare sits below the usual range. The buy signal. The band itself is returned as price_insights_low and price_insights_high.
- Why do some routes come back without a verdict?
- Google publishes the band for most well-travelled routes but not all. When it isn’t published, the fields are null and the checker shows fares without a gauge, honestly unjudged rather than guessed.
- What if there are no flights on my date?
- The API distinguishes a genuine empty result from a failed search with an X-Search-Status header. This tool shows you which one happened: “empty” is a real answer, “degraded” means try again.
- Can I run this from my own code?
- Yes. The card under the results shows the exact cURL, Python, or Node request that reproduces your check, pre-filled with your route and dates. A free RapidAPI key takes about a minute.
- How fast is a check?
- It is a live scan, not a cache read, so it tracks route complexity: trunk routes usually answer in a few seconds; dense or hard routes take longer. The API’s own listing says the same thing: live data costs latency.
The same check, from your own code
One POST, and the verdict field does the judging for you. Free tier on RapidAPI, no card to try.
Free tier: 10 requests/month. No card to try.