canonical: https://jentic.com/apis/flightqueue.com/flightqueue # FlightQueue API The FlightQueue API reports real-time airport intelligence for more than 8,000 airports, covering current security, check-in, and immigration wait estimates. It returns hourly wait-time predictions, FAA delay status, and historical wait patterns for a given airport, so an agent can judge when to leave for a flight. It lists the airports it supports, offers a bulk wait-times call for many airports at once, and lets a caller create or update an alert that fires when a wait time crosses a threshold. ## For AI agents Read real-time airport intelligence: current security, check-in, and immigration wait times, hourly predictions, FAA delay status, and historical patterns for a given airport, plus wait-time alerts. ## Scope Does not handle flight booking, gate assignments, or baggage tracking. Use for airport wait times, delays, and predictions only. ## Capabilities - Get current security, check-in, and immigration wait estimates for an airport - Read hourly wait-time predictions for an airport - Check FAA delay status for an airport - Pull historical wait-time patterns for an airport - List the supported airports - Create or update a wait-time alert - Fetch bulk wait times across many airports at once ## Use cases ### Agent departure timing An AI agent connected through Jentic advises a traveller when to leave for the airport by reading the current security, check-in, and immigration wait estimates and the hourly predictions for their departure airport, so the answer reflects live conditions rather than a fixed buffer, without the developer wiring the auth or paging logic. Example prompt: Read the current and predicted security wait times for a departure airport and recommend a leave-by time ### Delay-aware alerting A travel assistant creates a wait-time alert for a traveller's airport and checks FAA delay status so it can warn them the moment conditions worsen, turning the alert endpoint and the delay endpoint into a watch on a single airport. Example prompt: Create a wait-time alert for an airport and check its FAA delay status to warn the traveller of worsening conditions ### Operations dashboard An operations tool pulls bulk wait times across a set of hub airports in one call and reads each one's historical patterns, so a team can see where queues are building and compare the day against the airport's norm. Example prompt: Fetch bulk wait times for a set of hub airports and compare each against its historical pattern ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/airports` | List supported airports | | GET | `/airports/{iata}/wait-times` | Current security, check-in, and immigration wait estimates | | GET | `/airports/{iata}/predictions` | Hourly wait-time predictions | | GET | `/airports/{iata}/delays` | FAA delay status for an airport | | GET | `/airports/{iata}/historical` | Historical wait-time patterns | | POST | `/alerts` | Create or update a wait-time alert | | POST | `/airports/bulk` | Bulk wait times across many airports | ## Key resources - **Airports** — List supported airports and read their wait times, predictions, delays, and historical patterns - **Alerts** — Create or update an alert that fires when a wait time crosses a threshold ## 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:** 64 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 46 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 64 / 100 - **View full report:** https://jentic.com/apis/flightqueue.com/flightqueue/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 FlightQueue by hand means handling its bearer or API-key auth, keeping the agent key and developer key straight, and paging the per-airport wait, prediction, delay, and historical endpoints yourself. Through Jentic you install once, import FlightQueue from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** FlightQueue puts the IATA airport code in the URL path (`/airports/{iata}/...`), so a rule can pin your agent to read-only wait-time and delay lookups for airports. You choose the operations it may call, so write operations like creating an alert or the bulk Enterprise lookup are not included unless you add them. - **Credential handling:** Your FlightQueue 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 'get airport security wait times' or 'check an airport's FAA delay', and Jentic returns the matching FlightQueue operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Aviationstack** — Real-time flight status and schedules rather than airport queue and wait-time intelligence - **Amadeus** — Flight delay prediction and on-time performance that pair with airport wait data - **Duffel** — Books the flight whose airport FlightQueue is reporting on ## FAQ ### What authentication does the FlightQueue API use? The FlightQueue API accepts either a bearer token or an API key in the `X-API-Key` header, per its OpenAPI spec. The same keys work in both forms, and they come as an agent key or a developer key. 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 FlightQueue MCP server? You don't need an MCP server to give your agent FlightQueue. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the wait-time, prediction, and delay 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 FlightQueue API? Yes. Write a rule that allows only the read operations, such as current wait times, predictions, and delay status, so the agent can advise on timing but cannot create alerts or run bulk Enterprise lookups, and every call it makes is logged. ### Can I get predicted wait times with the FlightQueue API? Yes. The predictions endpoint returns hourly wait-time predictions for an airport by its IATA code, and the historical endpoint returns the airport's past wait patterns so an agent can compare the forecast against the norm. ### What are the rate limits for the FlightQueue API? The OpenAPI spec does not specify rate limits, and the bulk wait-times call is noted as an Enterprise feature. Check the vendor documentation at https://flightqueue.com/pricing for current plan limits. ### How do I check an airport's wait time through Jentic? Search Jentic for 'get airport security wait times', which returns the FlightQueue wait-times operation with its input schema, then pass the airport's IATA code and read the current estimate back. To run it on your own infrastructure, install Jentic One from its GitHub repo.