# 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.

## Quick facts

- 6 REST endpoints on https://api.flightpowers.com: POST /v1/flights/{oneway,roundtrip}, POST /v1/hotels/{search,by-name,rooms,resolve}
- OpenAPI spec: https://api.flightpowers.com/openapi.json
- 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): https://flights.flightpowers.com/mcp (flights, BYO key), https://hotels.flightpowers.com/mcp (hotels, BYO key), plus a free ad-supported server
- 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)
- 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. Same room, priced from the US, Germany, and Israel. Rate-parity monitoring from a single API.

## Pricing (read from the live RapidAPI listings on 2026-08-26; 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), 250 req/min
- 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

Every plan includes every endpoint; plans differ only on volume and rate limit. Billing is on RapidAPI. Apify actors are pay-per-event (hotels ≈ $4 per 1,000 searches, per the actor's own event table).

## Free tools (no signup)

- https://flightpowers.com/tools/google-flights-url-parser - decode/build Google Flights URLs, 100% client-side
- https://flightpowers.com/tools/flight-price-checker - live fare + Google's price band and verdict (rate-limited live demo)
- https://flightpowers.com/tools/cheapest-month-to-fly - sampled month scan as a price grid (rate-limited live demo)
- https://flightpowers.com/tools/hotel-price-by-country - one hotel priced from several markets via proxy_country (rate-limited live demo)

## Key pages

- https://flightpowers.com/pricing - plans, $/1k comparison, key checker
- https://flightpowers.com/flights-api and https://flightpowers.com/hotels-api - endpoint references with captured example responses
- https://flightpowers.com/mcp - MCP setup for any client
- https://flightpowers.com/ai-agents - agent recipes
- https://flightpowers.com/integrations - every surface (RapidAPI, MCP, n8n, Apify, Claude, ChatGPT, Cursor, Claude Code, OpenClaw)
- Agent recipes matrix: claude, chatgpt, cursor, claude-code, n8n, openclaw × 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>
- Docs: https://developers.flightpowers.com

## 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.