OAG API
OAG's Flight Info REST APIs are self-serve at developers.oag.com: schedules, status, connections, and push alerts, fronted by Azure API Management with subscription-key auth. The free trial is 14 days and 100 hits; paid tiers and enterprise data feeds are priced after signup or through sales.
Frequently asked questions
OAG scores A on Supergood's API Report Card. OAG's Flight Info REST APIs are self-serve at developers.oag.com: schedules, status, connections, and push alerts, fronted by Azure API Management with subscription-key auth. The free trial is 14 days and 100 hits; paid tiers and enterprise data feeds are priced after signup or through sales.
OAG has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
OAG (Official Aviation Guide) is the world's longest-running aviation data provider, founded in 1929 as a printed flight-schedule directory and today operating as the schedules-of-record authority for the global travel-distribution ecosystem.
Primary vertical: misc - Fleet / Trucking / Logistics (specifically the aviation/travel data layer; no native Supergood vertical maps perfectly, with Travel & Expense and POS/Hospitality as secondary neighbors for the corporate-booking and hotel-arrival use cases). A GDS or OTA ingests OAG schedules nightly (or via near-real-time refresh) as canonical input to its low-fare-search, connections-building, and timetable-display surfaces - then layers airline-direct NDC and live availability on top at shop time.
High inside aviation, travel distribution, airline IT, parametric insurance, and financial-analytics workflows; lower among indie developers and SaaS prototypers.
Yes - OAG's Flight Info API and enterprise data feeds sit directly in the operational path of any travel, hospitality, aviation, financial-analytics or parametric-insurance system that depends on accurate schedules, flight status, connections, or airfare data.
96 years old (founded 1929 in Chicago as the Official Aviation Guide of the Airways - inaugural February 1929 issue listed 35 airlines operating 300 flights).
Azure APIM subscription-key auth (header-based but a single shared secret per subscription) leaks into nginx, CloudFront, Datadog and any logging layer that captures full headers - mishandled keys are a recurring enterprise-integration concern. OAG explicitly tells developers not to enable CORS / not to call the API from the browser because the subscription key would leak - this forces every integrator to stand up a server-side proxy even for trivial dashboards. Full sourced list under Sources below.
Common alternatives include Cirium (FlightStats, Innovata, Diio, Ascend - RELX), FlightAware (Collins Aerospace / RTX), Flightradar24, AviationStack, Aviation Edge, AeroDataBox. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. As of August 2026 there is no official OAG MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. OAG doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.