canonical: https://jentic.com/apis/flightpowers.com/flightpowers # FlightPowers Travel Data API The FlightPowers Travel Data API returns live flight and hotel prices with the context to judge them. Flight searches run against live Google Flights results, and each itinerary carries Google's own historical price band and a low, typical, or high verdict plus a booking deep link. Hotel searches run against live Booking.com results, with a proxy country option so an agent can query any market's viewpoint, which is the basis for rate-parity and geo-pricing monitoring. A verify endpoint confirms a key works as cheaply as possible before a real search. ## For AI agents Search live flight and hotel prices with historical price context: one-way and round-trip flights with a low, typical, or high verdict, and hotels by destination, by name, or at room level. ## Scope Does not handle booking, payment, or itinerary storage. Use for live flight and hotel price search only. ## Capabilities - Search one-way flights with live Google Flights results - Search round-trip itineraries priced together - Search hotels at a destination with live Booking.com prices - Look up one hotel by name for availability and price in one call - Get room-level availability and pricing for a hotel - Resolve a hotel name to its Booking.com id - Verify that a key works before running a search ## Use cases ### Agent travel price check An AI agent connected through Jentic answers a trip question by searching live flight and hotel prices in one place, reading each flight's low, typical, or high verdict so it can tell the user whether now is a good time to book, without the developer stitching together separate flight and hotel providers. Example prompt: Search round-trip flights and hotels for a destination and report each flight's low, typical, or high price verdict ### Rate-parity monitoring A pricing tool checks a hotel's rate from several markets by setting the proxy country on each search, so it can see whether the same room is quoted differently by region and flag geo-pricing gaps against live Booking.com data. Example prompt: Search one hotel by name from several market viewpoints and compare the quoted rates for a parity gap ### Deal detection A fare-watch assistant searches itineraries and uses Google's historical price band on each result to surface only the ones priced below typical, attaching the booking deep link so a user can act on a flagged deal. Example prompt: Search one-way flights for a route and return only itineraries whose verdict is below typical, with their booking links ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/flights/oneway` | Search one-way flights | | POST | `/v1/flights/roundtrip` | Search round-trip itineraries | | POST | `/v1/hotels/search` | Search hotels at a destination | | POST | `/v1/hotels/by-name` | Look up one hotel by name | | POST | `/v1/hotels/rooms` | Room-level availability and pricing | | POST | `/v1/hotels/resolve` | Resolve a hotel name to its Booking.com id | | GET | `/v1/verify` | Check that a key works | ## Key resources - **Flights** — Search one-way and round-trip itineraries with a historical price verdict - **Hotels** — Search by destination, by name, or at room level, and resolve a hotel id - **Account** — Verify that a key works before searching ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 68 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 65 / 100 - AI-Readiness & Agent Experience: 50 / 100 - Agent Usability: 94 / 100 - Security: 53 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/flightpowers.com/flightpowers/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring FlightPowers by hand means bringing your own RapidAPI key, choosing which of the three accepted headers to send it in, and handling the separate flight and hotel request shapes yourself. Through Jentic you install once, import FlightPowers from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** FlightPowers carries the route, destination, and dates in the request body, so rules bound which operations your agent may call, not which market. Limit it to the flight and hotel search operations it needs, so write-style account actions are not in reach unless you add them. - **Credential handling:** Your FlightPowers key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search live flight prices' or 'look up a hotel by name', and Jentic returns the matching FlightPowers operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Amadeus** — Full travel platform with its own flight and hotel content rather than live Google Flights and Booking.com data - **Aviationstack** — Real-time flight status and schedules rather than priced offers - **Duffel** — Books a chosen flight, which FlightPowers does not do ## FAQ ### What authentication does the FlightPowers API use? The FlightPowers API accepts your RapidAPI key, sent in the `x-api-key` header, the `x-rapidapi-key` header, or as a bearer token, per its OpenAPI spec. Every request is billed to your own RapidAPI subscription. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's context. ### Is there a FlightPowers MCP server? You don't need an MCP server to give your agent FlightPowers. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the flight and hotel search operations on demand, without a separate server's tool definitions loaded into its context. ### Can I limit what my agent is allowed to do with the FlightPowers API? Yes. The search parameters travel in the request body, so a rule bounds which operations the agent may call rather than which destination. Allow only the flight and hotel search operations, so the agent can look up prices but reaches nothing else, with every call logged. ### Can I monitor regional hotel pricing with the FlightPowers API? Yes. The hotel search endpoints accept a proxy country so you can query a hotel's rate from any market's viewpoint, which is the basis for rate-parity and geo-pricing monitoring against live Booking.com data. ### What are the rate limits for the FlightPowers API? The OpenAPI spec does not specify a rate limit; because every request is billed to your own RapidAPI subscription, the limits follow your RapidAPI plan. Check the vendor documentation at https://flightpowers.com for current plan details. ### How do I search flights and hotels through Jentic? Search Jentic for 'search live flight and hotel prices', which returns the FlightPowers search operations with their input schemas, then issue a route or destination and read the priced results back. To run it on your own infrastructure, install Jentic One from its GitHub repo.