Integrations
One API, everywhere your stack already lives
The same live Google Flights and Booking.com data, reachable the way you already work: 6 REST endpoints, 3 hosted MCP servers, 8 open-source skills, a community n8n node, and pay-per-event Apify actors. One RapidAPI key, billed to you, everywhere.
Start here
RapidAPI: where the key and the bill live
Every integration on this page authenticates with a RapidAPI key. Two listings (Google Flights Live and Booking.com Live) with a free tier on each, account, metering, and invoicing all handled by RapidAPI.
How billing works →Every live surface
Pick your door
Each card is a full setup page: the connect block, what you can build, and honest notes on cost.
MCP servers
3 hosted serversHosted at flights. and hotels.flightpowers.com: add a URL and your key, no install. The config block is above the fold.
Claude
MCP connectorOne custom-connector URL and Claude quotes live fares with Google’s verdict mid-conversation.
ChatGPT
MCP connectorDeveloper-mode connector on the same servers: the key rides in settings, never in the chat.
Cursor
.cursor/mcp.jsonThe agent that writes your travel feature can also run it: live responses instead of guessed schemas.
Claude Code
8 open-source skillsnpx skills add mtnrabi/travel-agent-skills: cheapest dates, fare watch, rate-parity monitoring and more, MIT-licensed.
OpenClaw
ClawHub skillsTwo ClawHub listings (live Google Flights deals and Booking.com availability), installed with one line each.
Smithery
MCP registryThe three server listings on Smithery, and how its gateway passes your key through server config.
n8n
n8n-nodes-flightpowersA community node installed by name from Settings: fare-watch crons and rate-parity checks without writing HTTP requests.
Apify
pay-per-event actorsBoth APIs as actors with no monthly fee: the fit for occasional batch jobs with zero baseline volume.
REST API
6 endpoints + /v1/verifyapi.flightpowers.com direct: one POST, flat JSON, OpenAPI spec, and the same RapidAPI key you already have.
Skills (open source)
GitHub · MIT8 agent skills for flight and hotel pricing in a public repo: read them, fork them, run them.
Zapier and Make integrations are in review. The REST API works in both today via a webhook / HTTP-request step. The guides show the exact setup.
Questions, answered plainly
- Which integration should I start with?
- If you write code, the REST API: one POST returns flat JSON. If you use an MCP client (Claude, ChatGPT, Cursor), the hosted servers are a URL plus your key, nothing to install. If you automate in n8n, the community node. All of them read the same live data with the same key.
- Do the integrations cost extra?
- No. Every surface here is a different door to the same two RapidAPI subscriptions: you pay for API usage on your own plan, wherever the calls come from. The one exception is Apify, where the actors bill pay-per-event through Apify instead.
- Where do I get the key all of these use?
- From RapidAPI, on either listing’s pricing tab. The free tier is 10 requests/month with a hard cap (enough to verify your key works), and one key covers both APIs once you subscribe to each.
- Is there a Zapier or Make integration?
- In review, and we don’t publish doors that don’t open yet. The REST API already works in both today through a webhook / HTTP-request step. The guides show how.
Keep exploring
Related pages
Ready to judge a fare, not just fetch it?
Live Google Flights and Booking.com data, with the price band and verdict attached to every result. Free tier on RapidAPI, no card to try.
Free tier: 10 requests/month. No card to try.