Reservations
Reservationsreservations
Providers using this tag (69)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 9 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 22 Early or largely undocumented
Minimal 12 Almost no public developer surface
Unrated 2 Not yet scored
APIs with this tag (73)
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 →
Exemplar 2 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 21 Usable, with meaningful gaps to close
Thin 26 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 2 Almost no public developer surface
Companies reaching this through an API (38)
These companies publish an API, specification or operation carrying “Reservations” 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
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 67 providers in the APIs.io catalog tagged Reservations, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 36.1 | 26.5 | +9.6 | 67 |
| Developer Ergonomics | 28.9 | 23.4 | +5.5 | 67 |
| Operational Transparency | 19.2 | 14 | +5.2 | 67 |
| Discoverability | 63.6 | 61.2 | +2.4 | 67 |
| Contract Quality | 22.1 | 19.8 | +2.3 | 67 |
| Contract Governance | 6.4 | 6.4 | 0 | 67 |
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) | 10% | 10% | 0 |
| MCP server (first-party) | 12% | 13% | -1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 12% | 11% | +1 |
| Security | 97% | 97% | 0 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 13% | 14% | -1 |
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 69.3
- 2 Cvent Hospitality Cloud 64.3
- 3 Mews 61.5
- 4 Mews 59.8
- 5 Cobot 55.9
- 6 ROLLER 55.5
- 7 Quandoo 53.9
- 8 Amadeus 51.2
- 9 Peek 49.9
- 10 Lokki 48.1
- 1 Cvent Hospitality Cloud 53.2
- 2 LaFourchette 47.2
- 3 Cobot 46.9
- 4 Mews 39.2
- 5 GuestReady 37.1
- 6 Mews 36.7
- 7 SpotHero 35.9
- 8 AGL 35
- 9 Peek 33.8
- 10 Lokki 33.7
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.