You are picking an API for a travel product. You search the Flights tag on APIs.io and two names sit at the top: FlightAware at 59.1 and Amadeus at 57.1 on the Kin Score. Both are rated strong. They are 2.0 points apart. The question is simple: both of these say flights, so which one do you build on?
The post you are reading starts by putting the numbers in context. The Kin Score measures the public API surface, not the product and not the company. The Flights tag has 42 providers, and its scored members average 21.5. Both of your candidates sit more than 35 points above their own category. Amadeus wins four of the six facets.
Then the post tells you the answer turns on a fact the score does not yet carry. The Amadeus catalog record notes that the Self-Service developer portal was scheduled to be decommissioned on 17 July 2026. On the day of writing, test.api.amadeus.com, the base URL every one of its 28 API pages declares, no longer resolves in DNS. The Amadeus OpenAPI repository on GitHub is archived, last pushed in September 2024. The production host still answers. The self-service surface the score was built from is going or gone.
So you look at what you would actually be buying. The post says these are two different purchases that meet at one word. FlightAware sells flight data: real-time tracking assembled from air traffic control feeds, radar, ADS-B and satellite. You reach it through AeroAPI, a query-based REST API, and Firehose, a streaming feed for enterprise customers. Amadeus is the technology provider behind much of the travel industry. Its Amadeus for Developers door offered 40+ REST APIs across flights, hotels, destination content, cars and transfers, with a free, capped Test environment and a paid Production one.
Access is where they diverge most. FlightAware reads as freemium with self-serve signup, API key authentication, 5 plans and 6 rate-limit entries recorded. Amadeus reads as paid, onboarding unknown, no trial, OAuth 2.0 client credentials. Enterprise customers, the record says, keep access through Enterprise APIs, and those are not the APIs on these pages.
The number that matters most to you is callability. All 8 FlightAware contracts resolve to a live host. Only 2 of 28 Amadeus contracts do, 7.1 percent.
The facet breakdown explains how the ranking came out. Amadeus takes discoverability, contract quality, contract governance and developer ergonomics, which together carry 0.67 of the weight. FlightAware takes operational transparency, 84.2 to 23.7, and access clarity, 84.2 to 44.7. Those are the two widest gaps on the sheet, and they are enough to put FlightAware ahead on the base. In plain words, Amadeus is easier to start with, with SDKs in several languages, a public Postman workspace and a richer contract. FlightAware tells you more about how the API behaves and what it costs.
The post also warns you not to read the artifact counts at face value. Amadeus's page shows 18 Arazzo workflows, 106 collections, 810 JSON Schemas and 565 examples, and FlightAware shows none of those. But the workflows carry no first-party provenance marker and do not appear in Amadeus's own repository, so they are catalog work, not something Amadeus ships. Both agentic-access profiles are derived by the catalog, and so are FlightAware's 4 agent skills. FlightAware's governance score of 4.5 is its weakest number: no ruleset, no vocabulary, no declared conformance.
Here is the turn. The post does not defend its own ranking. It says the Flights tag ranks a decommissioned program second and the catalog has not caught up. The 2.0 points are real, and they are last quarter's. The catalog is filing the dead test host and the archived repository against the Amadeus record for the next rescore.
What you take away is a decision rule. If you need to know where an aircraft is, was or will be, FlightAware is the only one of these with that surface, and you can sign up, read the price and call it today. If you need to shop and book a trip, Amadeus is the only one with that surface, but the self-service road to it is closed, and the Enterprise route is a sales conversation, not a developer portal. A two-point gap between scores tells you less than whether the host answers.
Read the original: https://apis.io/2026/11/05/flightaware-vs-amadeus-two-points-apart-and-the-test-host-no-longer-resolves/