FlightPowers Travel Data API
68
AI ReadinessAI-Aware (B+)68/100
Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey, bearer7 EndpointsREST
For 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.
Use for: Search one-way flights for a date, Find round-trip flight options priced together, Search hotels at a destination, Look up a hotel's price by name
Not supported: Does not handle booking, payment, or itinerary storage. Use for live flight and hotel price search only.
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.
Install Jentic One Beta
Connect the FlightPowers Travel Data API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FlightPowers Travel Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflightpowers.com%2Fflightpowers" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflightpowers.com%2Fflightpowers" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with FlightPowers Travel Data API.
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
Patterns agents use FlightPowers Travel Data API for, with concrete tasks.
★ 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.
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.
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.
Search one-way flights for a route and return only itineraries whose verdict is below typical, with their booking links
Key Endpoints
7 endpoints — the flightpowers travel data api returns live flight and hotel prices with the context to judge them.
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
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
Jentic AI Readiness Score
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.
F
FlightPowers Travel Data API
- AI-Aware (B+)68/100
93
Foundational Compliance65
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience94
Agent Usability53
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
65
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
3%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
57%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
45%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
53%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
53
Security
Trust, risk posture, and security compliance.
Grade: CSignals: 1
53%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using FlightPowers Travel Data API through Jentic.
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.
GET STARTED