flightpowers.com valid

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.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T02:57:25.027Z. Cached copy · Source on flightpowers.com

# 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-10-23

## 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 se
…

Related sites

Explore similar publishers →

Category suggestions: other listed sites in AI and machine learning. These share a category. See the whole category →

Machine-readable: GET /v1/resolve?q=flightpowers.com · GET /v1/domain/flightpowers.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for flightpowers.com:
1. POST https://agentwebmap.com/v1/sites/flightpowers.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://flightpowers.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/flightpowers.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/flightpowers.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.