Integrations · Apify
The same data, pay-per-event
Both APIs also run as Apify actors, pay-per-event through your own Apify account. They're the right pick if your pipelines already live in Apify. Calling from your own code? The RapidAPI key is the simpler path, and the same key runs the paid MCP server for date scans.
The two actors
One click adds them to your console
The links below pre-add the actor to your Apify console after signup, no searching the store.
Google Flights Scraper
One-way and round-trip fares with airlines, layovers, Google's price band and low | typical | high verdict, and a booking link on every result. By the actor's own event table ($0.003 per lookup, $0.00001 per result), the lookup event alone is $3.00 per 1,000 flight lookups. One run is one route and one departure date (plus a return date on a round trip).
Booking.com Scraper
Live rates, availability, review scores and room types. By the actor's own event table ($0.005 per lookup, $0.00001 per result), a 25-property search costs about $0.0053 all in, and the lookup event alone is $5.00 per 1,000 hotel lookups. The unit is the search, not the result row.
Which door for which workload
Apify for Apify pipelines, RapidAPI for regular lookups
Same live data on every door. Pick by where your code runs and how often it calls.
Pick the actors when…
Your pipelines already live in Apify: runs, schedules, retries and datasets sit in the same console as your other actors, and the bill goes on your Apify account. You pay per search ($3.00 per 1,000 flight lookups, $5.00 per 1,000 hotel lookups, plus a fraction of a cent per run for results) and a month with no runs costs nothing on the actor.
Pick RapidAPI when…
You run lookups regularly or on a schedule from your own code: an app feature, an agent, a nightly fare check. One HTTP request per search and a fixed monthly bill. PRO is $10 for 2,500 flight searches, hotels PRO is $10 for 2,000, and flights takes 150 / 250 / 500 requests a minute by plan.
Pick the MCP server when…
You want a scan: a range of departure dates and a few destination airports in one prompt, from Claude, Cursor or ChatGPT. Only the MCP servers take a date range (the REST API and the actors take one date per request or run). It runs on the same RapidAPI key, and each date and destination combination counts as one search. See a real scan.
Recipes
Seven things to build with Apify
Each one is a full page: the connect block, the job in plain words, the exact call it makes, and the response fields your logic reads.
One-way flight search
Flights API · /v1/flights/oneway
Round-trip search
Flights API · /v1/flights/roundtrip
Price-insights check
Flights API · /v1/flights/oneway
Cheapest-date scan
Flights API · /v1/flights/oneway
Hotel search
Hotels API · /v1/hotels/search
Rate-parity check
Hotels API · /v1/hotels/by-name
Fare-alert cron
Flights API · /v1/flights/oneway
Questions, answered plainly
- How does pay-per-event billing work?
- Apify meters named events per run (a search performed, a result returned) and bills your Apify account for what actually happened. There’s no monthly subscription for the actor itself, so a month with no runs costs nothing on the actor.
- What does the hotels actor cost in practice?
- By its own event table ($0.005 per lookup plus $0.00001 per result and $0.00005 per run), a search returning 25 properties costs about $0.0053 all in. The lookup event alone is $5.00 per 1,000 hotel lookups. The unit is the search, not the result row, so a listing badge that divides by result rows looks cheaper than a search really is.
- What does the flights actor cost?
- By its own event table ($0.003 per lookup plus $0.00001 per result and $0.00005 per run), the lookup event alone is $3.00 per 1,000 flight lookups, and the result and start events add a fraction of a cent per run (a 25-result search is about $0.0033 all in). One run is one search: one route, one departure date (and a return date on a round trip).
- Can the actor scan a month of dates in one run?
- No. Each run searches one route and one departure date (plus a return date on a round trip), same as one request on the REST API, so a month of departure dates is about 30 runs. A range of departure dates and a list of destination airports in one call exist only in the flights MCP servers. The paid one runs on your RapidAPI key and counts each date and destination combination as one search.
- Do I need a RapidAPI key for the actors?
- No. The actors run under your Apify account and bill through Apify: they are the one surface on this site that doesn’t use a RapidAPI key.
- Is the data different from the API’s?
- No. Same live data, same fields: Google’s price band and low/typical/high verdict on flights, live Booking.com rates on hotels. What changes is the billing model and the runtime (an actor run instead of an HTTP request).
- When is RapidAPI the better fit?
- When you run lookups regularly or on a schedule from your own code. It’s one synchronous HTTP request per search instead of starting a run, the bill is a fixed monthly plan, and flights takes 150 / 250 / 500 requests a minute by plan. PRO is $10 for 2,500 flight searches (hotels PRO is $10 for 2,000). If you use the whole quota, the bigger flights plans cost less per search than the flights actor: flights ULTRA is $25 for 10,000 ($2.50 per 1,000).
Keep exploring
Related pages
Calling regularly from your own code? Get the key
PRO is $10 for 2,500 flight searches a month: same data, one HTTP request per search, a fixed bill. The same key runs the paid MCP server for date scans.
Free tier: 50 requests/month. No card to try.
Docs: the Flights API and the MCP servers.