Search Flights
search_flightsSearch for flights between cities or airports.
How it works ↓Pricing
Per call
$0.01
Model
flat
Pay only for what you use. No subscriptions.
Inputs
destination *
stringoptions
objectdepart_date *
stringorigin *
stringreturn_date
stringInput Parameters
Cost per run
Execution cost$0.01
About Search Flights
Search for flights between cities or airports. Provide city names or IATA codes (e.g., 'Austin', 'LAX') and departure date. City names often work better than airport codes. For round-trip flights, always provide a return_date. For one-way flights, omit the return_date parameter.
Frequently Asked Questions
Search for flights between cities or airports. Provide city names or IATA codes (e.g., 'Austin', 'LAX') and departure date. City names often work better than airport codes. For round-trip flights, always provide a return_date. For one-way flights, omit the return_date parameter.
Search Flights costs $0.01 per call on xpay. No subscription, no minimums. Pay only for the calls you make. New accounts get $5 in free credits.
Connect the Flight Search MCP endpoint to your client — Claude Code: claude mcp add --transport http flight-search "https://flight-search.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"; Cursor/Windsurf/Cline/VS Code: same URL in mcp.json. The agent will see search_flights as a callable tool with the input schema and run it directly. (Unified across all providers: https://mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY, then xpay_run with toolPath flight-search/search_flights.)
Yes — that's exactly what xpay is for. You don't need a Flight Search account or API key. Sign up at xpay.tools (Google or email), get $5 free credit, and run Search Flights immediately. Billing flows through your xpay balance.
Search Flights accepts 5 input parameters: destination, options, depart_date, origin, return_date. See the input schema and runnable form on this page for details and to test live.