Pricing
We are not the cheapest. Here is what a call returns.
Other Google Flights listings on RapidAPI sell at 32 cents per thousand calls. Ours starts at $4. Before the plan table, here is one real response so you can see what is in it and decide for yourself whether the difference buys you anything.
Are you an AI agent? Machine-readable pricing → (same file at /pricing.txt)
POST /v1/flights/oneway
{"departure_id":"LHR","arrival_id":"BCN","outbound_date":"2026-10-20"}
200 OK
x-search-status: ok
x-search-results: 5
x-search-attempts: 2
x-search-retries: 1
x-search-notes: upstream_connection
[
{
"price_range_in_relation_to_other_periods": "typical",
"price_insights_low": 50,
"price_insights_high": 110,
"from_airport": "London (LHR)",
"to_airport": "Barcelona (BCN)",
"departure_date": "2026-10-20",
"price": "$52",
"price_as_number": 52,
"duration": "2 hr 20 min",
"duration_seconds": 8400,
"airline": "Vueling | Iberia, British Airways",
"stops": 0,
"stops_info": [],
"departure_description": "8:50 PM on Tue, Oct 20",
"arrival_description": "12:10 AM on Wed, Oct 21",
"buy_link": "https://www.google.com/travel/flights?tfs=GjwSCjIwMjYtMTAtMjAi..."
}
// 4 more results, same shape
]Run against api.flightpowers.com on 2026-09-04 at 17:52 UTC. First of five results, buy_link cut at the query string. Nothing else edited. Fares move; re-run it yourself with the free tier.
price_insights_low / high
typical$52 against Google's own band for this route and date
Google's own price band comes back inside every result, so $52 is not a number floating on its own. It sits at the bottom of a $50 to $110 range. A scraper that returns a list of fares makes you build that context yourself, usually by storing history for weeks first.
x-search-status
This call took two attempts. The upstream connection dropped once, we retried, and the headers say so: attempts 2, retries 1, status ok. That is the contract. Every response tells you what happened behind it, so an empty array is never ambiguous and a partial result is never silently passed off as a complete one. How the header works.
Also in there and hard to fake: a working buy_link per result, layovers with durations, and price_as_number next to the display string so you are not parsing currency out of text.
The plans
Pay for volume, nothing else
Flights and hotels are separate APIs with separate plans. One RapidAPI account key works for both once you subscribe to each. No card for the free tier, no approval step, no feature gates.
Google Flights Live API
Open the live pricing tab →| Plan | Price / mo | Requests | $ / 1k req | Overage | Rate limit | |
|---|---|---|---|---|---|---|
| BASIC | Free | 10 / mo | — | hard cap | — | Get this plan → |
| PRO | $10 | 2,500 / mo | $4.00 | $0.003 / req | 150 / min | Get this plan → |
| ULTRArecommended | $25 | 10,000 / mo | $2.50 | $0.003 / req | 250 / min | Get this plan → |
| MEGA | $50 | 50,000 / mo | $1.00 | $0.001 / req | 500 / min | Get this plan → |
Swipe the table sideways for overage and rate limits.
Every plan on this API includes all of its endpoints; flights and hotels are separate subscriptions. Read from the live listing on 2026-09-11; the listing is authoritative.
Booking.com Live API
Open the live pricing tab →| Plan | Price / mo | Requests | $ / 1k req | Overage | Rate limit | |
|---|---|---|---|---|---|---|
| BASIC | Free | 10 / mo | — | hard cap | — | Get this plan → |
| PRO | $10 | 2,000 / mo | $5.00 | $0.006 / req | 25 / min | Get this plan → |
| ULTRA | $20 | 6,500 / mo | $3.08 | $0.003 / req | 25 / min | Get this plan → |
| MEGA | $50 | 25,000 / mo | $2.00 | $0.002 / req | 50 / min | Get this plan → |
Swipe the table sideways for overage and rate limits.
Every plan on this API includes all of its endpoints; flights and hotels are separate subscriptions. Read from the live listing on 2026-09-11; the listing is authoritative.
Live on RapidAPI: Google Flights Live API, 9.9 popularity, 99% service level, ~1112ms latency. Booking Live API, 9.7 popularity, 94% service level, ~8567ms latency.
Metrics retrieved from rapidapi.com/mtnrabi listings on 2026-09-01
The obvious objection
Why not the $0.40 per 1,000 listing
It is a fair question and the cheap listings are real. Here is what we found when we read their pages, and what we did not check.
| Listing | Entry plan | Per 1,000 | Free | What their page says |
|---|---|---|---|---|
google-flights4things4u-api4upro | Pro $14 / 35,000 | $0.40 | 110 / mo | Google Flights. 14 endpoints, including price graphs and date grids we do not have. 5 requests/second. |
google-flights2DataCrawler | Pro $12.99 / 40,000 | $0.32 | 150 / mo | Google Flights. 13 endpoints, multi-city included. No per-minute rate limit set on any plan. |
flights-skyntd119 | Pro $15 / 15,000 | $1.00 | 50 / mo | Its page names Skyscanner 15 times. Different source, so not the same payload as ours. |
sky-scrapperapiheya | Pro $9.99 / 10,600 | $0.94 | 20 / mo | Describes itself as reproducing skyscanner.com and booking.com data. Again, a different source. |
google-flights-live-apimtnrabi (us) | Pro $10 / 2,500 | $4.00 | 10 / mo | Google Flights. Two endpoints. Price band and verdict in every result, search-status headers on every response, 150 to 500 requests/minute. |
What we found
We pulled all four listing pages on 2026-09-04 and searched the same payload that carries their endpoint docs. None of them documents a price-insights band, a low / typical / high field, or any search-status header. Two of the four describe Skyscanner data rather than Google Flights, so they are not selling the same payload at a lower price, they are selling a different payload.
What we are not claiming
We read their listings. We did not buy a plan or call their APIs, so this is a claim about their published docs on one day, not about their servers. They are genuinely cheaper, their free tiers are genuinely bigger than our 10, and two of them ship endpoints we do not have at all: price graphs, date grids, multi-city. If those are what you need, buy theirs. We would rather say that than pretend.
Two questions people ask before they subscribe
Answers, up front
If you scan dates
“How fast can I go?”
One search is one request, so a 30-date scan costs 30 requests. Every paid tier fits that whole scan inside a single minute's allowance with room to spare, which is the point: you fire the dates in parallel and wait once, instead of pacing a queue.
- PRO · $10
- 150 req/min
- ULTRA · $25
- 250 req/min
- MEGA · $50
- 500 req/min
- BASIC · $0
- no per-minute limit set; the 10/mo cap binds first
Rate limits read off the live listing by npm run check-pricing, the same script that fills the table above. How the parallel scan works.
If you price round trips
“Do I have to staple two one-ways together?”
No. A round trip is one request and comes back as one priced itinerary: a real total_price for the pair, with both legs described in the same object. Two one-way searches added up give you a number no airline will sell you.
{
"total_price": "$389",
"total_price_as_number": 389,
"total_stops": 0,
"total_duration_seconds": 41820,
"price_insights_low": 180,
"price_insights_high": 385,
"price_range_in_relation_to_other_periods": "high",
"departure_flight_airline": "American",
"departure_flight_departure_description": "6:00 AM on Thu, Oct 15",
"departure_flight_arrival_description": "9:11 AM on Thu, Oct 15",
"departure_flight_duration": "6 hr 11 min",
"departure_flight_stops": 0,
"return_flight_airline": "American",
"return_flight_departure_description": "3:29 PM on Thu, Oct 22",
"return_flight_arrival_description": "11:55 PM on Thu, Oct 22",
"return_flight_duration": "5 hr 26 min",
"return_flight_stops": 0
}Same run window, 2026-09-04 at 17:49 UTC. First itinerary of the set, cut to the paired-leg fields. Response headers on this one: x-search-status: ok.
Which flights plan for which job
Price the job, not the tier
Flight plans shown; the same logic sizes a hotels plan.
PRO · $10
Alerts & agents
2,500 requests is a fare-watch checking 5 routes every morning with room to spare, or an MCP-connected agent used daily. At 150 req/min even a month-long scan is a single burst.
ULTRA · $25 · recommended
Products & dashboards
10,000 requests is 300+ searches a day: a fare-calendar feature, a route-monitoring dashboard, a bot with real users. $2.50 per 1k requests, 250 req/min.
MEGA · $50
Scans at scale
50,000 requests at $1.00 per 1k, our cheapest unit price, with 500 req/min and the lowest overage ($0.001). Built for heatmaps over many routes and market analysis.
From click to working key
Six steps, honestly counted
Two of them are RapidAPI's walls, not ours, but none needs approval and the free tier needs no card. Full guides: How to get a Google Flights API key and How to get a Booking.com API key.
- 1
Open the pricing tab
The buttons on this site land you there directly.
- 2
Create a RapidAPI account (or log in)
The wall. Standard signup; RapidAPI runs accounts and billing.
- 3
Pick a plan
BASIC is free, no card, no approval. Access is immediate.
- 4
Hit "Test Endpoint" on the Endpoints tab
Your key is bound automatically; the response renders in the browser.
- 5
Copy a code snippet
The Code Snippets tab emits your language with the key in place.
- 6
Verify the key below
Confirm it authenticates against the live API, the step RapidAPI leaves out.
Did my key work?
Paste the key RapidAPI gave you and we check it against GET /v1/verify on the live API. The key is used for that one request and never stored or logged.
Heads-up: the check itself is one real request against your hotels quota. That is how you know it works.
Prefer pay-per-use?
The same data as Apify actors
No subscription: you pay per event, metered by Apify. One click adds the actor to your Apify console.
Google Flights Scraper
One-way and round-trip fares with airlines, layovers, Google price insights and a booking link on every result, packaged as an actor. Pay-per-event; see the event table on the listing for current rates.
Booking.com Scraper
Live rates, availability and review scores. By the actor's own event table ($0.0037 per lookup, $0.00001 per result), a 25-property search costs about $0.004, roughly $3.70 per 1,000 hotel lookups. Priced per search, not per result row.
Rule of thumb: steady monthly volume is cheaper on RapidAPI (150 / 250 / 500 req/min and a fixed bill); occasional batch jobs with zero baseline fit Apify's pay-per-event model.
Questions, answered plainly
- Do flights and hotels share one plan?
- No. They are two listings on RapidAPI with different plans: flights runs $0 / $10 / $25 / $50 at 150 to 500 requests/minute, hotels $0 / $10 / $20 / $50 at 25 to 50. Subscribe to each API you use; the same account key then works for both.
- Where does billing actually happen?
- On RapidAPI. You subscribe to a plan on the listing’s pricing tab, RapidAPI issues the key and meters usage, and their invoice is your invoice. We never see your card. If your company already uses RapidAPI, there is no new vendor to onboard.
- The free tier is only 10 calls. What can I do with that?
- Enough to see the shape of the thing and not much else. Ten calls buys you a couple of one-way searches with the price band in the response, one round trip as a paired itinerary, and a look at the search-status headers. It will not survive a load test, and we are not going to pretend otherwise. Evaluate on the live demo and the free tools here first, because those run real requests on our key and leave your 10 alone, then follow the quickstart or the API key guide when you want the key in your own code. The 10 is under review and it may go up. Nothing is promised until it changes on the listing itself, so plan around 10.
- How do I move over from Amadeus or Kiwi?
- Both of those are access problems before they are pricing problems, so the migration guide starts there: which providers you can still sign up for today, what each one gates on, and what the request and response actually look like next to ours. Read Amadeus Self-Service alternatives, or the shorter side-by-side at FlightPowers vs Amadeus. The short version for both: there is no application form here, the free tier needs no card, and you can have a working key before you finish the guide.
- What counts as a request?
- A call to any endpoint is one request. The listings state this per plan. A round-trip search is one request. A 30-day flexible-date scan over REST is 30 requests (one per date), which is why the rate limits are sized the way they are.
- Do the plans differ in features?
- No. Within each API, every plan includes every endpoint. Plans differ only on monthly volume, overage price, and requests per minute. There is no feature gate to hit later.
- What happens when I exceed my quota?
- On paid plans the quota is soft: extra requests bill at the plan’s overage rate ($0.003/request on flights Pro and Ultra, $0.001 on Mega; $0.006 / $0.003 / $0.002 on hotels). The free tier is a hard cap: requests beyond 10 are rejected, not billed.
- What if I need more than 50,000 requests a month?
- Message through the RapidAPI listing. Custom volume plans are a normal thing there and the developer answers.
Pick a plan, get a key, make your first call
The free tier verifies your key in a minute. The Pro tier is $10, less than the hour you'd spend fighting a scraper.
Free tier: 10 requests/month. No card to try.