About
One developer, live travel data
I'm Matan Rabi, a software engineer. I build and run everything you see here: the APIs, the servers behind them, and this site. There is no team page because there is no team.
The short, honest story
FlightPowers started as a consumer product: a flight-search site for travellers, not a developer tool. To make it work I had to build the unglamorous layer underneath: the part that reads live Google Flights pages, survives markup changes and blocked requests, and can tell “there are no flights” apart from “the page wouldn't load.”
Running a consumer product on top of that layer taught me what flight-data infrastructure actually costs: not the happy path, but the retries, the consent walls, the empty responses that lie to you. Solving those problems well turned out to be worth more than the search site sitting on top of them.
So the data layer became the product. The APIs you can buy today are that same infrastructure, sold directly, with the failure handling exposed as response headers instead of hidden behind a UI, and Google's own price context attached to every fare.
How I run it
The rules this site holds itself to
You are reading marketing written by the person who also answers the bug reports. These are the constraints I keep on myself.
- No invented metrics, anywhere on this site. No uptime percentages, no latency claims, no customer counts. Every number you see traces to the live listings or to the code.
- Canned demos are labelled. Anything pre-recorded carries a “captured run” badge with the date it was captured. If it isn't labelled, it ran live.
- Failure modes are documented, not hidden. The API tells you when a search degraded instead of pretending an empty list is an answer: the whole mechanism is public.
- I answer. Both listings end with the same sign-off: “Message me. I keep improving this API and I answer.” That is not support-page boilerplate: the messages come to me and I reply to them personally.
What exists today
Everything the APIs power right now
One data layer, published on the surfaces developers and agents already use. All first-party, all maintained by me.
Google Flights Live API
RapidAPI listing: one-way, round-trip, price insights
Booking Live API
RapidAPI listing: hotel search, by-name, per-country pricing
Apify actors
The same data, pay-per-event: flights and hotels
3 hosted MCP servers
A URL your agent connects to, no install
n8n community node
n8n-nodes-flightpowers on npm
travel-agent-skills · 8 skills
Open source, MIT, on GitHub
Reach me
Want to talk?
Feature requests, custom volume, a data problem, or just a question about whether the API fits your build: the contact page lists the channels I actually watch.
See what the API returns before you decide
The demos and free tools on this site run real searches, and every canned example is labelled with its capture date. Judge the data, not the pitch.
Free tier: 10 requests/month. No card to try.