Integrations · RapidAPI
The marketplace where the billing lives
Both APIs are listed on RapidAPI. Whatever surface you connect through (REST, MCP, n8n, an agent), the key comes from here and the usage bills here. This page is the short version; the numbers are the live listings'.
Free tier on both listings: 10 requests/month. No card to try.
What RapidAPI handles
Four things you never build against us
RapidAPI sits between you and the API for exactly these. Everything else is direct.
The account
One RapidAPI login covers every API you use there. No FlightPowers account exists: there is nothing extra to create, verify, or forget.
The key
Issued the moment you subscribe, shown on the listing, bound automatically when you hit Test Endpoint. The same key authenticates on RapidAPI's host, on api.flightpowers.com, and on the MCP servers.
The metering
Every request counts against your plan's monthly quota and per-minute rate limit, visible in RapidAPI's developer dashboard: their counter, not our word.
The invoice
RapidAPI charges your card and issues the invoice. Overage on paid plans bills at the listed per-request rate; the free tier is a hard cap, never a surprise charge.
The two listings
One subscription per API, every endpoint included
Plans read from the live listings on 2026-09-11. The listing is authoritative. Plans differ only on volume and rate limit; no endpoint is ever gated.
Google Flights Live API rapidapi.com/mtnrabi/api/google-flights-live-api
Get a key →| Plan | Price / mo | Requests | $ / 1k req | Overage | Rate limit |
|---|---|---|---|---|---|
| BASIC | Free | 10 / mo | — | hard cap | — |
| PRO | $10 | 2,500 / mo | $4.00 | $0.003 / req | 150 / min |
| ULTRArecommended | $25 | 10,000 / mo | $2.50 | $0.003 / req | 250 / min |
| MEGA | $50 | 50,000 / mo | $1.00 | $0.001 / req | 500 / min |
Swipe the table sideways for overage and rate limits.
Every plan on this API includes all of its endpoints; flights and hotels are separate subscriptions. Read from the live listing on 2026-09-11; the listing is authoritative.
Booking.com Live API rapidapi.com/mtnrabi/api/booking-live-api
Get a key →| Plan | Price / mo | Requests | $ / 1k req | Overage | Rate limit |
|---|---|---|---|---|---|
| BASIC | Free | 10 / mo | — | hard cap | — |
| PRO | $10 | 2,000 / mo | $5.00 | $0.006 / req | 25 / min |
| ULTRA | $20 | 6,500 / mo | $3.08 | $0.003 / req | 25 / min |
| MEGA | $50 | 25,000 / mo | $2.00 | $0.002 / req | 50 / min |
Swipe the table sideways for overage and rate limits.
Every plan on this API includes all of its endpoints; flights and hotels are separate subscriptions. Read from the live listing on 2026-09-11; the listing is authoritative.
From click to working key
Six steps, condensed
Two of them are RapidAPI’s walls, not ours, and none needs approval.
- 1Open the pricing tab. The buttons on this page land there directly.
- 2Create a RapidAPI account, or log in. This is the wall, and it is theirs.
- 3Pick a plan. BASIC is free with no card; access is immediate on every public plan.
- 4Hit “Test Endpoint” on the Endpoints tab. Your key is bound automatically.
- 5Copy a code snippet in your language, key already in place.
- 6Verify the key against the live API, the step RapidAPI leaves out.
The full walkthrough (with the key checker for step 6 built in) is on the pricing page.
The marketplace question
What happens to your code if a listing disappears
Fair question, and the honest answer is a base URL and a key, not a rewrite. Here is exactly why, and the part of it that genuinely does depend on RapidAPI.
A marketplace listing is a distribution channel. It is not where this API lives. The same six endpoints answer on our own domain, and the same key authenticates on both hosts, so moving between them is one line.
# through the marketplace
POST https://google-flights-live-api.p.rapidapi.com/api/google_flights/oneway/v1
x-rapidapi-key: $KEY
x-rapidapi-host: google-flights-live-api.p.rapidapi.com
# on our own domain
POST https://api.flightpowers.com/v1/flights/oneway
x-api-key: $KEYThe spec is a document you can keep
flightpowers.com/openapi.json is served from our domain at a fixed path. Generate your client from it, commit the file, and your integration does not depend on a listing page rendering.
The MCP servers are on our domain too
flights.flightpowers.com and hotels.flightpowers.com, listed in the official MCP registry as com.flightpowers/google-flights and com.flightpowers/booking. A gateway listing is one more door, never the only one.
The client code is open and readable
The agent skills are MIT-licensed on GitHub. Every call they make is in the repository, so nothing about how this API is used is locked inside a wrapper you cannot read.
What genuinely does depend on RapidAPI
Billing. RapidAPI issues the key, meters the usage, and sends the invoice. If that door closed, the key and the invoice would have to move somewhere else. The endpoints, the spec and the response shapes would not.
Recipes
Seven things to build with RapidAPI
Each one is a full page: the connect block, the job in plain words, the exact call it makes, and the response fields your logic reads.
One-way flight search
Flights API · /v1/flights/oneway
Round-trip search
Flights API · /v1/flights/roundtrip
Price-insights check
Flights API · /v1/flights/oneway
Cheapest-date scan
Flights API · /v1/flights/oneway
Hotel search
Hotels API · /v1/hotels/search
Rate-parity check
Hotels API · /v1/hotels/by-name
Fare-alert cron
Flights API · /v1/flights/oneway
Questions, answered plainly
- Why is billing on RapidAPI instead of on this site?
- Because it removes a vendor. RapidAPI runs the accounts, keys, metering, and invoicing for thousands of APIs. If your company already uses it, procurement is already done, and your usage across APIs lands on one invoice. We never see your card.
- Is it one key for both APIs?
- One RapidAPI key works across the APIs you subscribe to, but flights and hotels are separate listings with separate subscriptions and quotas. Subscribe to each you need; the key in your code stays the same.
- Is the free tier enough to evaluate?
- Honestly, no. BASIC is 10 requests/month with a hard cap: enough to verify your key and see the response shape. Evaluate with the live demo and free tools on this site; they run real requests on our key.
- Is there an approval step?
- No. Every public plan on both listings has request-approval disabled: subscribing is immediate, and the free tier needs no card.
- Does the key work outside RapidAPI’s own host?
- Yes. The same key authenticates against api.flightpowers.com (as x-rapidapi-key, x-api-key, or a Bearer token) and against the hosted MCP servers. Usage from every surface meters against the same subscription.
- What happens when I hit my quota?
- On paid plans, overage billing per request at the rate shown in the tables above. On the free tier the cap is hard: request 11 is rejected, not billed.
Keep exploring
Use the key you just got
Get the key once, use it everywhere
REST, MCP, n8n, skills: every surface on this site runs on the same RapidAPI subscription. Free tier to verify, $10 to actually build.
Free tier: 10 requests/month. No card to try.