# HotelOne

> HotelOne lists independent hotels, inns and motels with their own booking sites. AI assistants can search them, check live availability and prices, answer guests' questions and book — through an MCP server or a REST API. No sign-up or key is needed to search or to get a booking link.

The all-in-one platform for independent hotels: a white-labeled booking website, an AI agent that answers calls and chats like your best front-desk clerk, and one dashboard that keeps your booking channels in sync.

## Connect

- [MCP server (all hotels)](https://hotelone.site/api/mcp): Streamable HTTP, stateless JSON-RPC (protocol 2025-06-18, 2025-03-26, 2024-11-05). Add it as a custom connector or remote MCP server; no authentication needed.
- One hotel's own MCP server: https://hotelone.site/api/mcp/hotels/{propertyId} — the same tools for that hotel only (no hotel id needed).
- [REST API](https://hotelone.site/api/agents/v1) and its [OpenAPI 3.1 description](https://hotelone.site/openapi.json) — import as a GPT Action or any OpenAPI tool.
- [Agent card](https://hotelone.site/.well-known/agent-card.json) · [MCP manifest](https://hotelone.site/.well-known/mcp.json) · [Full details for models](https://hotelone.site/llms-full.txt)
- [How to connect ChatGPT, Claude, Grok, Le Chat and others](https://hotelone.site/assistants)

## Booking flow

1. search_hotels (GET /api/agents/v1/hotels) with a place and, if known, dates (YYYY-MM-DD), guests and rooms.
2. check_availability (GET /api/agents/v1/hotels/{propertyId}/availability) for the hotel the person picks.
3. get_booking_link (POST /api/agents/v1/booking-links): a checkout link with everything filled in — the person opens it and confirms in one tap. This is the default.
4. No screen? request_booking (POST /api/agents/v1/booking-requests): the hotel team confirms and sends a link.
5. With a hotel's API key ("book" scope): create_booking (POST /api/agents/v1/bookings) makes a confirmed booking, paid at the hotel.

One booking can mix room types (e.g. 1 King and 2 Doubles): pass items (each roomTypeId and its rooms) instead of roomTypeId. Always read back the hotel, room, dates, guests and total and get a clear yes before request_booking or create_booking. Quote prices only from tool results. Questions about a hotel: ask_hotel. Existing bookings: find_booking (code + last name).

## Limits

- 120 requests a minute per IP address (600 a minute with an API key).
- Booking requests: 10 an hour per IP (60 with a key). Bookings: 60 an hour per key.
- Booking lookups: 20 an hour per IP (200 with a key).
- With API keys, a hotel's keys together also share an hourly allowance (100 bookings, 100 booking requests, 300 lookups), and each hotel takes a limited number of booking requests an hour from callers without a key.
- Over the limit: HTTP 429 with Retry-After (MCP tool calls return an error result the model can explain).

## Optional

- [Hotel directory](https://hotelone.site/properties)
- Contact: hello@hotelone.site