Travel
Providers using this tag (361)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 6 Solid coverage with minor gaps
Developing 34 Usable, with meaningful gaps to close
Thin 61 Limited public surface area
Emerging 115 Early or largely undocumented
Minimal 144 Almost no public developer surface
APIs with this tag (96)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Strong 8 Solid coverage with minor gaps
Developing 20 Usable, with meaningful gaps to close
Thin 39 Limited public surface area
Emerging 26 Early or largely undocumented
Minimal 3 Almost no public developer surface
Companies reaching this through an API (19)
These companies publish an API, specification or operation carrying “Travel” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Where this tag sits
361 providers carry this tag directly, and 412 counting the 11 narrower tags below — 51 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 340 providers in the APIs.io catalog tagged Travel, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Governance | 5.6 | 6.3 | -0.7 | 340 |
| Discoverability | 57.3 | 58.1 | -0.8 | 340 |
| Access Clarity | 22.4 | 26.5 | -4.1 | 340 |
| Operational Transparency | 9.5 | 13.7 | -4.2 | 340 |
| Developer Ergonomics | 18.7 | 23.2 | -4.5 | 340 |
| Contract Quality | 13 | 17.6 | -4.6 | 340 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 14% | 14% | 0 |
| MCP server (first-party) | 11% | 12% | -1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 11% | 11% | 0 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 2% | 2% | 0 |
| Governance rules | 9% | 14% | -5 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Oracle Hospitality 73.4
- 2 Booking.com 65.8
- 3 StayingAPI 64.8
- 4 Mews 60.1
- 5 Airalo 58.5
- 6 General Services Administration 58
- 7 ReefAPI 57.7
- 8 Wego 53.2
- 9 TUI Group 53.1
- 10 Engine 53
- 1 StayingAPI 59.4
- 2 Beyond 55.9
- 3 Wego 54.7
- 4 Autoura 51.3
- 5 HelloSafe 49.3
- 6 Landing 46.9
- 7 FlightLabs 46.7
- 8 Booking.com 46.1
- 9 Sabre 46
- 10 Viator 45.9
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.