agentleFS
scavio-aiscavio-ai/skills/skills/google-flights-api/SKILL.md

google-flights-api

Skill48 starsChanged 33 days agoMITView on GitHub

Google Flights route search by date as structured JSON: price, airline, total duration, stops and per-leg detail across best_flights and other_flights. Round-trip, one-way and multi-city, with cabin class, stops, airline and sort filters. One endpoint on the v2 engine, 1 credit per request.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search Google Flights for a route and date and return structured JSON — price, airline, duration, stops, and per-leg details.

    line 20
  2. Distinctive:

    Use this skill when the user asks to:

    line 24
  3. Very specific:

    When the balance runs out the API answers 402 with a JSON body carrying billing_url.

    line 47
  4. Distinctive:

    Every request costs 1 credit.

    line 59
  5. Very specific:

    Read best_flights[] and other_flights[].

    line 66
  6. Distinctive:

    Never fabricate prices, airlines, times, or durations.

    line 153
  7. Very specific:

    If no flights are returned, relax stops, airline filters, or try nearby dates.

    line 164
  8. Very specific:

    If SCAVIO_API_KEY is not set, prompt the user to export it before continuing.

    line 165

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Google Flights API - Route Search, Prices, Carriers, Stops

Search Google Flights for a route and date and return structured JSON — price, airline, duration, stops, and per-leg details. One credit per request.

When to trigger

Use this skill when the user asks to:

  • Find flights between two airports on given dates
  • Compare airfares, airlines, durations, or number of stops
  • Plan round-trip, one-way, or multi-city itineraries
  • Filter flights by cabin class, stops, or specific airlines

Setup

Get a free API key at scavio.dev (50 free credits to get started, no card required):

export SCAVIO_API_KEY=sk_live_your_key

If you do not have a key yet

An agent running this skill without SCAVIO_API_KEY set will get 401 on every call below. The whole path from nothing to a working key is self-serve:

  1. Sign up at dashboard.scavio.dev - email or Google, no card required.
  2. A key is created for the account automatically at signup. It is on the dashboard under API Keys, ready to copy.
  3. A new account starts with 50 credits. Endpoints in this skill cost 1 credit each unless the table below says otherwise.

When the balance runs out the API answers 402 with a JSON body carrying billing_url. Topping up needs no code change - the same key keeps working. The smallest purchase is 2,500 credits for $25, and monthly plans work out cheaper per credit if the usage is steady rather than one-off.

Endpoint

POST https://api.scavio.dev/api/v2/google/flights
Authorization: Bearer $SCAVIO_API_KEY

Every request costs 1 credit.

Workflow

  1. Provide departure_id and arrival_id (IATA codes) and an outbound_date (YYYY-MM-DD).
  2. For a round trip (type: 1, the default) also pass return_date. Use type: 2 for one-way, type: 3 for multi-city.
  3. Refine with travel_class, stops, adults, sort_by, and airline filters.
  4. Read best_flights[] and other_flights[]; each itinerary lists its flights legs, price, total_duration, and airline.

Parameters

ParameterTypeDefaultDescription
departure_idstringrequiredOrigin IATA (comma-separated allowed, e.g. JFK)
arrival_idstringrequiredDestination IATA (e.g. LAX)
outbound_datestringrequiredDeparture date YYYY-MM-DD
typenumber11 round trip, 2 one way, 3 multi-city
return_datestring--Required when type=1
adultsnumber1Adult passengers (1-9)
childrennumber--Children (0-9)
infants_in_seatnumber--Infants in seat (0-4)
infants_on_lapnumber--Lap infants (0-4)
travel_classnumber--1 economy, 2 premium, 3 business, 4 first
stopsnumber--0 any, 1 nonstop, 2 <=1 stop, 3 <=2 stops
sort_bynumber--1 top, 2 price, 3 departure, 4 arrival, 5 duration, 6 emissions
include_airlinesstring--Restrict to these airlines
exclude_airlinesstring--Exclude these airlines
hlstring--UI language
glstring--Geo country
currencystring--Currency code (e.g. USD)

Example

import requests

# Your key from https://scavio.dev. Load it from your environment or secret
# store in real code - keep it out of source control.
API_KEY = "sk_your_key_here"

response = requests.post(
    "https://api.scavio.dev/api/v2/google/flights",
    headers={"Authorization": f"Bearer {API_KEY}"},
    json={
        "departure_id": "JFK",
        "arrival_id": "LAX",
        "outbound_date": "2026-09-10",
        "return_date": "2026-09-17",
        "type": 1,
        "travel_class": 1,
        "stops": 1,
        "sort_by": 2,
        "currency": "USD",
    },
)
data = response.json()
for f in data.get("best_flights", []):
    legs = f["flights"]
    print(f["price"], f["total_duration"], "min",
          legs[0]["airline"], legs[0]["departure_airport"]["id"], "->",
          legs[-1]["arrival_airport"]["id"])

Response

{
  "best_flights": [
    {
      "flights": [
        {
          "departure_airport": { "id": "JFK", "time": "2026-09-10 08:00" },
          "arrival_airport": { "id": "LAX", "time": "2026-09-10 11:25" },
          "airline": "Example Air",
          "flight_number": "EA 123",
          "duration": 385
        }
      ],
      "total_duration": 385,
      "price": 342,
      "type": "Round trip"
    }
  ],
  "other_flights": [],
  "response_time": 1980,
  "credits_used": 1,
  "credits_remaining": 994,
  "cached": false
}

Guardrails

  • Each call costs 1 credit.
  • Never fabricate prices, airlines, times, or durations. Only return API data.
  • departure_id and arrival_id must be IATA codes; outbound_date is YYYY-MM-DD.
  • A round trip (type=1) requires return_date.
  • Prices reflect the requested currency; state the currency when quoting fares.

Failure handling

  • 400 means an invalid parameter (e.g. round trip without return_date, bad IATA/date) — fix and retry.
  • 401 means the API key is invalid or missing. Check SCAVIO_API_KEY.
  • 429 means rate or usage limit exceeded. Wait before retrying. See rate limits.
  • 502 / 503 mean upstream is temporarily unavailable. Wait a few seconds before retrying.
  • If no flights are returned, relax stops, airline filters, or try nearby dates.
  • If SCAVIO_API_KEY is not set, prompt the user to export it before continuing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.