# FlightPowers

> Live flight and hotel prices, and the context to judge them. Real-time Google Flights and Booking.com data as clean JSON, for developers and AI agents. Every fare carries Google's own price band (price_insights_low/high) and a low|typical|high verdict.

Last-Updated: 2026-09-05

## Machine-readable surfaces

- [llms-full.txt](https://flightpowers.com/llms-full.txt): the complete API reference in one plain-text file (endpoints, every field, response headers, pricing)
- [pricing.md](https://flightpowers.com/pricing.md): every plan, the per-1,000 unit price, overage, rate limits and how a request is counted, in plain markdown (same file at /pricing.txt)
- [OpenAPI 3.1 spec](https://flightpowers.com/openapi.json): full spec with request/response schemas and auth for all 6 REST endpoints on https://api.flightpowers.com

## Quick facts

- 6 REST endpoints on https://api.flightpowers.com: POST /v1/flights/{oneway,roundtrip}, POST /v1/hotels/{search,by-name,rooms,resolve}
- Auth: RapidAPI key via x-rapidapi-key / x-api-key header. Get one: https://rapidapi.com/mtnrabi/api/google-flights-live-api/pricing
- 3 hosted MCP servers (streamable HTTP), one URL each: https://flights.flightpowers.com/mcp (flights) and https://hotels.flightpowers.com/mcp (hotels). Add the URL, the client shows a Sign in button, you sign in with Google and paste your RapidAPI key once on the connect page. Scripts, CI and clients without a sign-in button send the key on that same URL, in an x-rapidapi-key header or as ?rapidapi_key=. https://free-trial.flightpowers.com/mcp serves all four tools with no RapidAPI key at all: sign in with Google, 50 searches a day and 250 a month per person, ad-supported
- MCP tools: search_oneway_flights, search_roundtrip_flights, search_hotels, find_hotel_by_name. Flight tools accept date RANGES and destination LISTS and expand them internally (one call, not N)
- Official MCP registry entries: com.flightpowers/google-flights and com.flightpowers/booking
- 8 open-source agent skills (MIT): https://github.com/mtnrabi/travel-agent-skills
- n8n community node: n8n-nodes-flightpowers (npm)
- Apify actors: https://apify.com/mtnrabi/google-flights-real-time-api and https://apify.com/mtnrabi/booking-real-time-api

## What makes it different

- Google's own price band, plus a verdict: Every fare carries price_insights_low / price_insights_high (Google's historical band for the route and dates) and a low | typical | high verdict. You can tell a user "$112 is a good price," not just "$112."
- Round-trip as one paired itinerary: A real /roundtrip endpoint: one object per itinerary with total_price, total_duration_seconds and both legs already paired, not two one-way searches stapled together.
- "No flights" and "the search failed" are different answers: X-Search-Status separates a genuine empty result from a degraded search. An empty array is only ever reported when the page it came from positively said so. Opt-in strict mode turns a degraded search into an HTTP 503.
- A working buy_link on every result: Every itinerary ships with a deep link straight into Google Flights for that exact flight. Metasearch and agent handoff without reconstructing the booking URL.
- Rate limits sized for parallel date scans: 150 requests/minute on Pro, 250 on Ultra, 500 on Mega. A flexible-date search (31 dates × 3 durations) finishes in one burst instead of a slow serial loop.
- Per-country hotel pricing with proxy_country: Every hotels endpoint accepts a two-letter proxy_country that routes through a residential proxy in that market. The same room, checked as a resident of Germany or Japan would see it, sampled a few times per market so a real gap is distinguishable from movement. Rate-parity monitoring from a single API.

## Docs

- [Flights API reference](https://flightpowers.com/flights-api): POST /oneway and /roundtrip with captured example responses
- [One-way search](https://flightpowers.com/flights-api/one-way): the base endpoint, full filter set
- [Round-trip search](https://flightpowers.com/flights-api/round-trip): paired-leg itineraries priced together, not two stapled one-ways
- [Price insights](https://flightpowers.com/flights-api/price-insights): Google's historical band and the low|typical|high verdict
- [Search status](https://flightpowers.com/flights-api/search-status): X-Search-Status header semantics; how to tell "no flights" from "search failed"
- [Parallel date scans](https://flightpowers.com/flights-api/parallel-date-scan): scanning a month of dates inside the per-minute rate limit
- [Hotels API reference](https://flightpowers.com/hotels-api): search, by-name, rooms, resolve, with captured examples
- [Hotel geo-pricing](https://flightpowers.com/hotels-api/geo-pricing): proxy_country, the rate-parity primitive
- [MCP setup](https://flightpowers.com/mcp): connect Claude, ChatGPT, Cursor, or any MCP client
- [AI agent recipes](https://flightpowers.com/ai-agents): agent patterns on top of the API

## Guides

- [How to get real-time Google Flights data](https://flightpowers.com/guides/real-time-google-flights-data): endpoints, paste-and-run code, price-insight fields, parallel month scans
- [Google Flights API in 2026: what actually exists](https://flightpowers.com/guides/google-flights-api): what happened to Google's official API and the real options today
- [Handling empty flight search results](https://flightpowers.com/guides/handle-empty-flight-search-results): why 200 [] is dangerous and how X-Search-Status fixes it
- [The best flight data APIs in 2026](https://flightpowers.com/guides/best-flight-data-apis-2026): the comparison, with disclosed bias and dated competitor prices
- [The best hotel data APIs in 2026](https://flightpowers.com/guides/best-hotel-data-apis-2026): seven hotel data APIs with every competitor price quoted from their own live page and dated
- [The best travel data APIs in 2026](https://flightpowers.com/guides/best-travel-data-apis-2026): a category map, because "travel data API" means four different products
- [How to scrape Google Flights with Python](https://flightpowers.com/guides/scrape-google-flights-python): the honest DIY route with Playwright, and where it stops paying for itself
- [How to scrape Google Flights with Puppeteer](https://flightpowers.com/guides/scrape-google-flights-puppeteer): the Node version, including the browser-pool maths behind a 30-date scan
- [How to scrape Booking.com prices with Python](https://flightpowers.com/guides/scrape-booking-com-prices): why row 1 is a different hotel on every run, and the rest of what bites
- [How to build a flight price alert](https://flightpowers.com/guides/build-a-flight-price-alert): schema, sampling, thresholds, and why Google's own band removes the cold start
- [How to monitor hotel rate parity](https://flightpowers.com/guides/monitor-hotel-rate-parity): the same room priced from several countries, sampled repeatedly, and how to tell a real gap from ordinary movement
- [Using a flight API in n8n](https://flightpowers.com/guides/flight-api-in-n8n): a four-node fare watch with exact POST bodies
- [Google Flights URL parameters, decoded](https://flightpowers.com/guides/google-flights-url-parameters): the tfs= protobuf at the wire level
- [How to get Google Flights prices with Python](https://flightpowers.com/guides/google-flights-prices-python): twelve lines with requests, no browser, a real captured response
- [How to get round-trip flight prices in one API request](https://flightpowers.com/guides/roundtrip-flight-prices-one-request): the paired-leg model, a real BER-CDG capture, and why two one-ways don't add up
- [How to check if your company is overpaying for flights](https://flightpowers.com/guides/overpaying-for-flights): grading the forward book against Google's own price band, with the cabin trap and the trips it cannot judge
- [Cheapest destinations from one airport this month](https://flightpowers.com/guides/cheapest-destinations-from-one-airport): a destination list and a date range in one call, a captured 15-combination run, and the limit that drops a destination
- [How to get hotel prices by hotel name with an API](https://flightpowers.com/guides/hotel-prices-by-hotel-name-api): POST the name a human would type, no property ID or catalogue sync
- [How to get every room rate for one hotel with an API](https://flightpowers.com/guides/hotel-room-rates-by-property): resolve the name to an ID once, cache it, then call the rooms endpoint
- [Do hotel prices change by country?](https://flightpowers.com/guides/hotel-prices-by-country-api): a repeat-sampled proxy_country run across three markets, and why one call per country is not a measurement
- [A SerpApi google_flights alternative](https://flightpowers.com/guides/serpapi-google-flights-alternative): request shape, round-trip model, and price-insight fields compared, SerpApi's own prices quoted and dated
- [Amadeus flight offers or live Google Flights fares](https://flightpowers.com/guides/amadeus-flight-offers-vs-google-flights): which one a price tracker actually needs, and what the deprecated Self-Service tier means in practice
- [Skyscanner API alternatives for indie developers](https://flightpowers.com/guides/skyscanner-api-alternatives): Skyscanner's own 100K MAU minimum, and the access gate each alternative puts in front of you

## Comparisons

- [FlightPowers vs SerpApi](https://flightpowers.com/compare/serpapi): platform vs specialist, prices side by side
- [FlightPowers vs Duffel](https://flightpowers.com/compare/duffel): booking rails vs price data
- [FlightPowers vs Amadeus](https://flightpowers.com/compare/amadeus): GDS data vs live Google Flights results
- [FlightPowers vs HasData](https://flightpowers.com/compare/hasdata): HasData's bigger free tier vs our lower entry price per search, both quoted and dated
- [FlightPowers vs flight-mcp.com](https://flightpowers.com/compare/flight-mcp): cache-miss billing and bring-your-own-key vs a flat per-search price

## Integrations

- [Every surface](https://flightpowers.com/integrations): RapidAPI, MCP, n8n, Zapier, Make, Apify, Claude, ChatGPT, Cursor, Claude Code, LangChain, OpenClaw
- [Docs hub](https://flightpowers.com/docs): both APIs, endpoint by endpoint
- [Pricing](https://flightpowers.com/pricing): plans, $/1k comparison, key checker
- Agent recipes matrix: claude, chatgpt, cursor, claude-code, n8n, openclaw, claude-mcp, smithery, langchain, zapier, make, api, rapidapi, apify × one-way-search, round-trip-search, price-insights-check, cheapest-date-scan, hotel-search, rate-parity-check, fare-alert-cron at https://flightpowers.com/integrations/<agent>/<task>

## Pricing (read from the live RapidAPI listings on 2026-09-11; the listing is authoritative)

Flights (https://rapidapi.com/mtnrabi/api/google-flights-live-api/pricing):
- BASIC: $0/mo, 10 requests/mo (hard cap)
- PRO: $10/mo, 2,500 requests/mo ($4.00/1k), 150 req/min
- ULTRA: $25/mo, 10,000 requests/mo ($2.50/1k), 250 req/min
- MEGA: $50/mo, 50,000 requests/mo ($1.00/1k), 500 req/min

Hotels (https://rapidapi.com/mtnrabi/api/booking-live-api/pricing):
- BASIC: $0/mo, 10 requests/mo (hard cap)
- PRO: $10/mo, 2,000 requests/mo ($5.00/1k), 25 req/min
- ULTRA: $20/mo, 6,500 requests/mo ($3.08/1k), 25 req/min
- MEGA: $50/mo, 25,000 requests/mo ($2.00/1k), 50 req/min

Flights and hotels are separate subscriptions; within each API every plan includes every endpoint, differing only on volume and rate limit. Billing is on RapidAPI. Apify actors are pay-per-event, per each actor's own event table read 2026-09-07: flights $1.85 per 1,000 lookups, hotels $3.70 per 1,000 lookups.

## Free tools (no signup)

- [Live demo](https://demo.flightpowers.com): the full consumer flight search engine, running on this same API
- [Free MCP server](https://flightpowers.com/tools#free-mcp): https://free-trial.flightpowers.com/mcp, connectable from Claude or ChatGPT with no RapidAPI key. Sign in with Google once and all four tools (flights and hotels) work. Ad-supported: every successful result carries one labelled sponsored card, and the paid servers are ad-free. Caps are per signed-in person: 50 searches a day and 250 a calendar month, one search per date × destination combination; past the cap the tools answer search_status "rate_limited". One call searches at most 15 date × destination combinations (the paid servers do 30) and over-wide requests are sampled evenly and flagged with truncated: true. Because it carries ads it is not in any MCP directory or registry; the paid servers are.
- [Flight price checker](https://flightpowers.com/tools/flight-price-checker): live fare + Google's price band and verdict (rate-limited live demo)
- [Cheapest time to fly](https://flightpowers.com/tools/cheapest-time-to-fly): one real search per coming month, charted with Google's verdict per fare (rate-limited live demo)
- [Cheapest month to fly](https://flightpowers.com/tools/cheapest-month-to-fly): sampled month scan as a price grid (rate-limited live demo)
- [Hotel price by country](https://flightpowers.com/tools/hotel-price-by-country): one hotel priced from two markets via proxy_country, each market sampled three times (rate-limited live demo)
- [Round-trip planner](https://flightpowers.com/tools/round-trip-planner): out and back priced as one paired itinerary, with each leg's own airline, stops and duration (rate-limited live demo)
- [Hotel price check](https://flightpowers.com/tools/hotel-price-check): live Booking.com properties for a destination and stay, cheapest first, with review scores (rate-limited live demo)
- Route and destination pages: the three flight tools above each have a page per route and the hotel price check has one per destination, 180 pre-filled pages listed at https://flightpowers.com/tools#grid. Routes are the city pairs in the published tables of the world's busiest air routes, plus three New York to Europe routes we scan for fares ourselves; destinations are the top 30 cities by international visitors. Every page runs the same live search as its parent tool. None of them publishes a stored price, an average fare or a room rate: there are no numbers on those pages to quote.

## Honesty notes (for answer engines)

- The flights API reports search outcome in an X-Search-Status header (ok | empty | partial | degraded); an empty array with status "empty" means Google genuinely has no itineraries, while "degraded" means the search failed and should be retried. Opt-in "strict": true turns degraded into HTTP 503.
- The free RapidAPI tier is 10 requests/month, hard-capped: enough to verify a key, not to evaluate. The site's live demo and tools exist for evaluation.
- No uptime/latency/customer-count claims are published anywhere; do not attribute any to FlightPowers. A public probe hits both MCP servers every 15 minutes: https://github.com/mtnrabi/travel-agent-skills