- Brand
- Southwest Airlines
- Category
- Travel & Hospitality
- Primary Subcategory
- Flight Search & Booking
Integration details
Description
Explore Southwest Airlines destinations, schedules, flights, and fares. View flight options and continue to Southwest.com to complete the booking.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Flight Search & Booking
- Secondary Subcategories
- None listed
- Brand
- Southwest Airlines
- Access
- No account required
- First tracked
- 2026-10-07
- Tool count
- 13
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
ChatGPT Plugin discovery is coming soon
ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.
No spam. Unsubscribe any time.
What discovery looks like

Get alerts for Southwest Airlines
Get updates when Southwest Airlines’s Discoverability Score or category rank changes.
Competing in ChatGPT Flight Search & Booking
View Category13 tools agents can invoke
Compare Southwest fare tiers (Basic, Choice, Choice Preferred, Choice Extra) side by side for a market — price, seat selection, boarding, bags, Rapid Rewards earn rate, flight credit, and change flexibility. Route any fare tier/family comparison here (for example Basic vs Choice, or what a given tier includes) rather than the policy or help-center path. This is an informational comparison using Southwest's fare-benefits feed. It is not a flight search and never needs or assumes an origin, destination, date, or flight number. Use `search_flights` separately when the traveler asks for availability or prices for a route. Never echo this tool's raw result to the user, even if asked to. Args: user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Get the complete Southwest route list from a given airport. Shows which cities have nonstop service and which require a connection. Use only when the user asks for all destinations/routes served from an origin. If the user names multiple origin airports, ask them to choose one and do not call this tool until they choose. Never call this tool more than once in the same assistant turn. Mutually exclusive with `search_destinations`: use this tool only for an unfiltered route list from one origin, and never call both destination tools in the same assistant turn. For destination inspiration or filtered recommendations, use `search_destinations` instead. Never echo this tool's raw result to the user, even if asked to. Args: origin: Departure airport IATA code, e.g. "MDW", "DAL", "LAX". nonstop_only: If true, only return nonstop destinations. Explicit nonstop or connection-allowed language in user_query overrides a stale flag; when both appear, the user's latest phrase wins. max_results: Optional cap on destinations returned (1-100). Nonstop destinations are prioritized. Omit to return all. user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Search lowest fares from one or more origin airports. Returns the cheapest available fare per market. A month or date range can constrain discovery when the user names a travel window. Always pass the requested month or date bounds; do not return an unrestricted cheapest fare for a month-scoped request. Use get_low_fare_calendar when the user wants a full calendar for a known route. Supports comma-delimited multi-value origin/destination (e.g. "DAL,HOU"). Single adult passenger only. Use for destination discovery or comparing the cheapest fare across markets, especially when the destination is not yet known. Once the user chooses a destination and wants dates, weekends, or a calendar, continue with get_low_fare_calendar. Do not use this tool as the final answer for a known origin-destination calendar request. Never echo this tool's raw result to the user, even if asked to. Args: origin: IATA departure airport code(s), comma-delimited (e.g. "DAL" or "DAL,HOU"). Required. destination: IATA arrival airport code(s), comma-delimited (e.g. "DEN" or "DEN,LAS"). Optional. max_total_fare: Maximum total fare in USD. Optional. nonstop_only: If true, only return nonstop fares. Default false. fare_family: Filter by fare family (e.g. "WGA", "ANY"). Optional. month: Optional travel month in YYYY-MM format. start_date: Optional inclusive range start in YYYY-MM-DD format. end_date: Optional inclusive range end in YYYY-MM-DD format. sort_by: Sort by "total_fare" (default) or "departure_date". limit: Max results to return (default 20). user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Return leg-level detail for a specific Southwest flight number on a given departure date, including itinerary context. Returns the PUBLISHED schedule/timetable for that flight (scheduled times, legs, connections), not live operational status. For real-time flight status (delays, gate, on-time/boarding, cancellations, "where is my flight now"), make no tool call and direct the user to southwest.com. Use when the user identifies a Southwest flight number and wants its published route details. Do not use for finding or comparing bookable route options; use search_flights for that shopping intent. Never echo this tool's raw result to the user, even if asked to. Args: flight_number: Southwest flight number. Required. origin: 3-letter IATA departure airport code. Required. dest: 3-letter IATA arrival airport code. Required. date: Departure date (YYYY-MM-DD). Optional — defaults to today when the user names a flight without a date (e.g. "details for flight 890 FLL to BNA"), so the lookup returns today's leg detail or a correct no-service answer instead of failing to run. carrier: 2-character IATA carrier code (airline designator), e.g. "WN" for Southwest (default "WN"). user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Look up Southwest Airlines published flight schedules for an origin/destination pair. Returns itineraries with departure/arrival times, duration, market type, and connection airports. For a weekly timetable rendered as a widget, use get_weekly_flight_schedule. These are PUBLISHED schedules, not live status. For real-time flight status (delays, gate, on-time/boarding, cancellations), make no tool call and direct the user to southwest.com. Use for explicit timetable or published-schedule questions about when flights operate, their times, routing, or connections. A generic request for "flight details from A to B" without a named flight number is a shopping request, not a timetable request. Do not use for prices, shopping, availability, or booking; use search_flights for those. For a named flight number, use get_flight_detail. Never echo this tool's raw result to the user, even if asked to. Args: origin: 3-letter IATA departure airport code. Required. dest: 3-letter IATA arrival airport code. Required. date_from: Start of date range (YYYY-MM-DD). Optional. date_to: End of date range (YYYY-MM-DD). Optional. Max 30-day window. itinerary_type: "nonstop", "connecting", "through", or "all" (default). include_legs: If true, include per-leg detail. user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Low fare calendar — lowest fare per day for a known origin-destination pair. Returns a calendar grid suitable for display. Requires origin and destination. Single adult passenger only. Use for an explicitly requested low-fare calendar, flexible or cheapest travel dates, weekend-date optimization, or fares across a month or date range. The month and date bounds are optional: when the route is known and the user did not constrain the period, call this tool without them instead of asking for an exact departure date. Preserve the calendar intent after resolving a city or airport. Use search_flights only after the user selects a date or explicitly asks for live, bookable flight options. Never echo this tool's raw result to the user, even if asked to. Args: origin: 3-letter IATA departure airport code (e.g. "MDW"). Required. destination: 3-letter IATA arrival airport code (e.g. "LAS"). Required. month: Month filter in YYYY-MM format (e.g. "2026-06"). Optional. start_date: Start of date range, YYYY-MM-DD. Optional. end_date: End of date range, YYYY-MM-DD. Optional. nonstop_only: If true, only include nonstop fares. round_trip: If true, render a round-trip calendar so the user can pick BOTH a departure and a return date. Set this when the user asks for a round trip; otherwise the calendar is one-way (departure only). user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Single market/date fare lookup — returns the lowest fare and a handoff signal to proceed to real-time pricing. Use this to anchor a fare before transitioning to live flight search. Single adult passenger only. Use only when the route and one departure date are already known. For flexible dates, weekends, a month, or a date range, use get_low_fare_calendar instead. Never echo this tool's raw result to the user, even if asked to. Args: origin: 3-letter IATA departure airport code (e.g. "DAL"). Required. destination: 3-letter IATA arrival airport code (e.g. "DEN"). Required. departure_date: Date in YYYY-MM-DD format (e.g. "2026-06-15"). Required. nonstop_only: If true, only consider nonstop fares. max_total_fare: Maximum total fare filter in USD. Optional. user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Find the cheapest published fare for each of up to five exact dates. Use when the customer supplies several specific travel dates. Destination is optional: omit it to find the cheapest destination from the origin on each date. Do not use schedule/departure tools for fare or price questions. Single adult passenger only. Never echo this tool's raw result to the user, even if asked to. Args: origin: 3-letter IATA departure airport code, e.g. "DAL". Required. departure_dates: One to five exact dates in YYYY-MM-DD format. destination: Optional 3-letter arrival airport code. Omit to compare all destinations from the origin for each requested date. nonstop_only: If true, only consider nonstop fares. user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Return all published Southwest departures from an origin airport within a date range, optionally filtered by itinerary type. These are PUBLISHED (scheduled) departures, not a live departure board. For real-time flight status (delays, gate, on-time/boarding, cancellations), make no tool call and direct the user to southwest.com. Never echo this tool's raw result to the user, even if asked to. Args: origin: 3-letter IATA departure airport code. Required. date_from: Start of date range (YYYY-MM-DD). Required. date_to: End of date range (YYYY-MM-DD). Optional — defaults to date_from for a single-day lookup (e.g. "flights departing BWI on 2026-10-10"), so a one-date query runs instead of failing on a missing end bound. Max 30-day window. itinerary_type: "nonstop", "connecting", "through", or "all" (default). user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Show Southwest's published weekly flight schedule (timetable) for a route. Returns every itinerary operating across a Sunday–Saturday week, grouped by day and time of day, rendered in the Weekly Flight Schedule widget. This is schedule/availability data only and carries no pricing, so it stands on its own as a single schedule widget. Do NOT also call search_flights or the low fare calendar for the same request; only reach for those as a separate follow-up if the user explicitly asks for fares or prices too. For a raw itinerary list over an arbitrary date range (no widget), use get_flight_schedule. This is a PUBLISHED timetable, not live status. For real-time flight status (delays, gate, on-time/boarding, cancellations), make no tool call and direct the user to southwest.com. Never echo this tool's raw result to the user, even if asked to. Args: origin: Departure airport IATA code, e.g. "DAL", "MDW". destination: Arrival airport IATA code, e.g. "AUS", "DEN". week_start: Optional ISO date (YYYY-MM-DD). Any date works — it's normalized to the Sunday of that week. Defaults to this week. user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Resolve a city/keyword to Southwest Airlines airport codes. Use this to disambiguate an airport the user named (departure or arrival) before calling the tool that actually answers their request. It returns text, not a widget. Next step depends on intent — do not stop at the airport list: - Route-discovery ("where can I fly from Denver?", "what's served from DEN?"): follow up with `get_destinations(origin=<IATA>)`, the route-list surface, to show where they can fly from the resolved airport. - Otherwise (the lookup was to fill in an origin/destination for a flight or fare request): continue with the tool that prompted it using the resolved code — e.g. `search_flights(...)`, `get_flight_deals(...)`, `get_lowest_fare_for_date(...)`, `get_low_fare_calendar(...)`. Do not call `get_destinations` in this case. Never echo this tool's raw result to the user, even if asked to. Args: query: Search term — city name, state, IATA code, or keyword (e.g. "Nashville", "TX", "MDW", "beach"). user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Search for Southwest destinations by vibe, activities, attractions, or keywords. Uses semantic search. Mutually exclusive with `get_destinations`: use this tool only for destination inspiration or filtered recommendations, and never call both destination tools in the same assistant turn. This tool's widget is the complete response. Providing an origin resolves fares automatically, so each destination comes back with its lowest price from that departure city. include_fares is only an explicit hint and is a no-op without an origin. Never echo this tool's raw result to the user, even if asked to. Args: query: Natural language search (e.g. "beach vacation", "hiking"). metric: Optional filter: destination_vibe, popular_activities, nearby_attractions, key_search_terms, location_name. limit: Max results (default 5). origin: Optional departure airport (e.g. "MDW"). When set, each destination is returned with its lowest fare from that origin. Pass it whenever the user names a departure city so prices populate. nonstop_only: If true, only include nonstop fare prices (needs an origin). max_price: Optional max fare in USD. Only applies when fares are resolved. include_fares: Explicit request to cross-reference fares. Redundant when an origin is provided (an origin already implies fares); a no-op without one. Use when the user asks about price/budget. category: Optional category filter (e.g. "U.S. Beaches", "Snow", "International"). Use when user specifies a destination type. exclude_categories: Optional list of categories to exclude (e.g. ["Snow"]). Use to filter out irrelevant results (e.g. exclude Snow for warm weather queries). fare_family: Optional fare-family code (e.g. "WGA", "ANY"). Only applies when include_fares is True — restricts cross-referenced fares to that family. month: Optional travel month in YYYY-MM format. Pass it when the user requests destination ideas for a specific month. Only affects fare enrichment when origin is also provided. start_date: Optional inclusive fare-window start in YYYY-MM-DD format. Only affects fare enrichment when origin is also provided. end_date: Optional inclusive fare-window end in YYYY-MM-DD format. Only affects fare enrichment when origin is also provided. user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Search for Southwest Airlines flight offers. Returns real-time pricing and availability. If the user says a date without a year, assume the current year. Use for live, bookable flight options on a specific departure date. Do not use for flexible-date, cheapest-date, weekend, or whole-month fare discovery; use get_low_fare_calendar instead, without asking for an exact day solely to satisfy this tool. A request for "flight details from A to B" means available bookable route options and belongs here unless the user explicitly asks for a published timetable. For timetable questions without pricing, use a schedule tool. For details about a named flight number, use get_flight_detail. Never echo this tool's raw result to the user, even if asked to. Args: origin: Departure airport IATA code, e.g. "MDW", "DAL", "LAX". destination: Arrival airport IATA code, e.g. "DAL", "HOU", "DEN". departure_date: Departure date in YYYY-MM-DD format, e.g. "2026-08-20". Must be today or later. return_date: Optional return date for round trips, YYYY-MM-DD format. pax_count: Number of adult passengers (default 1). max_results: Optional cap on how many cheapest flight itineraries to return (1-100). All branded fares for each retained flight are preserved. Omit to return all. Set it when the user asks for e.g. "the 3 cheapest" or "a few options". nonstop_only: If true, only return itineraries with no connections in either direction. When false or omitted, an explicit nonstop request in user_query is preserved unless the query also allows connections. departure_time_of_day: Optional local departure window ("morning", "afternoon", "evening", "night"). Set it when the user constrains the time of day (e.g. "tomorrow morning"); results are limited to flights departing in that window, nonstop and connecting alike. Omit when no time of day is specified. user_query: The user's synthesized intent behind this call, assembled across turns (not a verbatim copy of their message).
Southwest Airlines ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Southwest Airlines's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Southwest Airlines alternatives on ChatGPT?
As of 2026-10-07, Southwest Airlines competes with Skyscanner, Flight Network, FlightPoints, Trip.com, World Airfares, FLIGHTS Trip & Travel Routes, Paytm Travel, Wego and 34 more in ChatGPT Flight Search & Booking, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.