Google Flights
Arcade.dev LLM tools for getting flights via Google Flights
4.1.0Google Flights Toolkit
Arcade toolkit that enables LLMs to search flights, resolve itineraries, and look up airports via the SerpApi Google Flights API.
Capabilities
- Airport lookup — Resolve city names, country names, or airport names to IATA codes, including metropolitan codes (e.g., NYC, LON) that span multiple airports.
- One-way & round-trip search — Search Google Flights for one-way or round-trip itineraries in a single call; results include direct
google_flights_urlbooking links. - Multi-city / open-jaw search — Search bundled multi-leg itineraries that are priced as a unit, typically cheaper than summing individual one-way fares.
- Booking options resolution — Resolve a
booking_tokenfrom any flight search to the airlines and OTAs selling that specific itinerary, with optional POST hand-off data for backend integrations.
Secrets
SERP_API_KEY — A SerpApi API key used to authenticate all Google Flights requests. Obtain it by creating an account at SerpApi, then copying the private API key from your SerpApi dashboard. Free-tier accounts include a limited monthly search quota; paid plans are required for higher volume. The key must have access to the Google Flights engine — no additional per-engine scoping is needed beyond a valid active SerpApi subscription.
Configure secrets in Arcade at https://docs.arcade.dev/en/guides/create-tools/tool-basics/create-tool-secrets or via the dashboard at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(4)
| Tool name | Description | Secrets | |
|---|---|---|---|
Resolve a ``booking_token`` to the airlines and OTAs selling that itinerary.
Pass a ``booking_token`` returned by ``search_flights`` or
``search_multi_city_flights`` to get the vendors selling that
specific flight. The token encodes the route, dates, cabin class,
and passenger counts (every segment for multi-city), so there are
no ``travel_class``, ``num_adults``, or ``num_children`` parameters;
supplying a cabin or party size would silently disagree with the
itinerary the token was issued for.
Leave ``include_booking_post_data`` off (the default) when an LLM
is comparing prices; turn it on only when a backend needs to
rebuild the vendor hand-off, since the POST body is multiple
kilobytes per option. | 1 | ||
Find IATA airport codes for a city, country, or airport name.
Metropolitan codes (NYC, LON, TYO, PAR, ...) are accepted as a
``departure_airport_code`` or ``arrival_airport_code`` in flight
searches and mean "any airport in this city". | 1 | ||
Search Google Flights for one-way or round-trip itineraries.
For a trip where the traveler returns to their origin, issue a
single call with both ``outbound_date`` and ``return_date`` set.
Do NOT issue two separate one-way searches in opposite directions
and sum the prices: airlines price round-trip fares independently
from one-way fares, so the sum of two cheapest one-ways is rarely
equal to the cheapest round-trip and is typically more expensive.
Each returned itinerary carries a ``google_flights_url`` that opens
that specific pre-selected flight on Google Flights, so you can hand
the user a booking link straight from these results without a
separate booking-options lookup. | 1 | ||
Search Google Flights for a multi-city (open-jaw) itinerary.
Use this for trips that are neither a simple one-way nor a round-trip
(e.g. an open-jaw three-leg trip that ends back at the origin).
The open-jaw bundle is typically cheaper than the equivalent set
of one-way searches summed; never substitute multiple
``search_flights`` calls for a single multi-city query.
Each returned itinerary carries a ``google_flights_url`` that opens
that specific pre-selected itinerary on Google Flights, so you can
hand the user a booking link straight from these results without a
separate booking-options lookup. | 1 |