Is my key billed to me?

Not to RapidAPI. This path bills pay-per-event through your own Apify account, so an idle month costs nothing. The RapidAPI subscription and the Apify actor are two separate doors to the same data; you need one, not both.

Does this need a server of mine?

No. The actor runs on Apify’s infrastructure, and runs, retries and result storage live in your Apify console alongside your other actors.

On this path, whatever the actor’s own event table charges for the events a run fires. There is no monthly plan and no minimum. The current rates are on the actor listing, which is the only place they are authoritative. If you would rather have a fixed monthly bill and synchronous HTTP, the RapidAPI plans are the other door: see /pricing.

Recipe · Flights API

One-way flight search with Apify

The agent searches live Google Flights data and answers with fares it can actually judge: every result carries Google’s historical price band and a low | typical | high verdict, so “is the price any good” is a field read, not a guess. The buy_link hands the user a working booking deep link.

Try the actor on Apify →All Apify recipes

Pay-per-event on your own Apify account. No monthly plan.

Step 1 · Connect

Run the actor

Pay-per-event through your own Apify account: no monthly plan, and an idle month costs nothing. The input field names and the endpoint values are the actors’ own published input schemas, read from api.apify.com on 2026-09-02. Nothing to subscribe to on RapidAPI for this path.

run the flights actor

curl -X POST "https://api.apify.com/v2/acts/mtnrabi~google-flights-real-time-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"endpoint":"oneway","from_airport":"LHR","to_airport":"JFK","departure_date":"2026-10-13","currency":"usd"}'

Billed per event on your own Apify account. No RapidAPI subscription needed for this path.

Step 2 · The job

The job

The job in plain words. In Apify you express it as the configuration below instead of a prompt.

“Find me a nonstop JFK to Cancun flight on January 1 and tell me if the price is any good.”

Step 3 · Under the hood

The actor input

Paste this into the actor’s Input tab, or send it as the JSON body of a run. Field names come from the actor’s own published input schema.

actor input

// actor: mtnrabi~google-flights-real-time-api
{
  "endpoint": "oneway",
  "from_airport": "JFK",
  "to_airport": "CUN",
  "departure_date": "2027-01-01",
  "currency": "usd",
  "limit": 5
}

Step 4 · Read the response

Fields your logic reads

The response is flat JSON. These are the fields this recipe branches on, with what each one means.

pricestring

The fare as Google Flights displays it: “$56”. The numeric twin price_as_number rides alongside for sorting and arithmetic.

price_insights_lownumber | null

The bottom of Google’s historical price band for this route and dates. Null when Google doesn’t publish a band: treat the fare as unjudged, not bad.

price_insights_highnumber | null

The top of the band. A fare above it is expensive for the route by Google’s own history.

price_range_in_relation_to_other_periods"low" | "typical" | "high" | null

Google’s verdict on the current fare against that band, the single field alerting, ranking, and “book now” logic branch on.

buy_linkstring (URL)

A Google Flights deep link that reopens this exact itinerary. Hand it to the user; it just works.

Questions, answered plainly

Is my key billed to me?: Not to RapidAPI. This path bills pay-per-event through your own Apify account, so an idle month costs nothing. The RapidAPI subscription and the Apify actor are two separate doors to the same data; you need one, not both.
Does this need a server of mine?: No. The actor runs on Apify’s infrastructure, and runs, retries and result storage live in your Apify console alongside your other actors.
What does it cost?: On this path, whatever the actor’s own event table charges for the events a run fires. There is no monthly plan and no minimum. The current rates are on the actor listing, which is the only place they are authoritative. If you would rather have a fixed monthly bill and synchronous HTTP, the RapidAPI plans are the other door: see /pricing.

Also works with

One-way flight search, elsewhere in your stack

One-way flight search in Claude One-way flight search in ChatGPT One-way flight search in Cursor One-way flight search in Claude Code One-way flight search in n8n One-way flight search in OpenClaw One-way flight search in Claude Desktop One-way flight search in Smithery One-way flight search in LangChain One-way flight search in Zapier One-way flight search in Make One-way flight search in REST One-way flight search in RapidAPI

More recipes

More to build in Apify

Round-trip search

Flights API · search_roundtrip_flights

Price-insights check

Flights API · search_oneway_flights

Cheapest-date scan

Flights API · search_oneway_flights

Hotel search

Hotels API · search_hotels

Rate-parity check

Hotels API · find_hotel_by_name

Fare-alert cron

Flights API · search_oneway_flights

Get live flight and hotel data

Live Google Flights and Booking.com data as clean JSON. Free tier on RapidAPI, no card to try.

Get a key on RapidAPI →See pricing

Free tier: 10 requests/month. No card to try.