Skip to content

Integrations

One API, everywhere your stack already lives

The same live Google Flights and Booking.com data, reachable the way you already work. Pick a door; each page has the connect block and what to build.

Start here

One key opens every door

Every integration authenticates with a RapidAPI key. Two listings (flights and hotels, separate plans), free tier on each, metering and invoicing handled by RapidAPI.

How billing works →
Get a flights key →Get a hotels key →

Free tier: 10 requests/month. No card to try.

The recipe matrix

Every surface, every job

The same seven jobs, written out for each surface: the connect block, the exact call, and the fields your logic reads. Pick the row you already work in.

Questions, answered plainly

Which integration should I start with?
If you write code, the REST API. If you use an MCP client (Claude, ChatGPT, Cursor), the hosted servers: a URL plus your key. If you automate in n8n, Zapier, or Make, start from that tile. Every door reads the same live data with the same key.
Do the integrations cost extra?
No. Every surface here is a different door to the same RapidAPI subscriptions: you pay for API usage on your own plan, wherever the calls come from. The 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, hard-capped: enough to verify your key. Flights and hotels are separate subscriptions; one account key covers both once you subscribe to each.
Is there a native Zapier or Make app?
Not listed yet; both are in review, and we don’t publish doors that don’t open. The REST API works in both today through the HTTP request step, and the Zapier and Make pages here show the exact module setup.

Get live flight and hotel data

Live Google Flights and Booking.com data as clean JSON. Free tier on RapidAPI, no card to try.

Free tier: 10 requests/month. No card to try.