HotelUse documentation
Give your agent hotel search, provider price comparisons, room rates and hotel information. Use the HTTP API or MCP.
Start with the Quickstart · Get an API key · Explore live requests
Your hotel workflow
Start with search_hotels for a destination and itinerary. Use a returned HotelUse ID with get_hotel for hotel information, or get_room_rates for room options and terms.
Three tools, one account
| Tool | HTTP endpoint | What it returns |
|---|---|---|
| search_hotels | POST /v1/hotels/search | Search hotels |
| get_hotel | POST /v1/hotels/get | Get hotel information |
| get_room_rates | POST /v1/rates/rooms | Get room rates |
Real production examples
Every reference page includes a response captured from https://www.hoteluse.dev. This capture uses Hilton Bellevue, 2026-11-12 to 2026-11-14, 2 adults, 1 room, USD. Collected 2026-10-21 17:50:47 UTC.
| Provider | Lowest stay total |
|---|---|
| expedia | $489.44 USD |
| booking | $489.45 USD |
| agoda | $489.45 USD |
| brek | $255.58 USD |
The room endpoint returned 242 offers across four providers, including 4 Booking room IDs and 56 Booking rate products. See the actual room offers. Captured prices are historical; run a new request for current availability.
Filters and result order
Filters & sorting: star classification, guest-review score and count, facilities, property types, distance, full-stay budgets, cancellation and breakfast. The same filters work through HTTP and MCP.
Built for agents
Documentation index · Full Markdown corpus · OpenAPI 3.1 · Agent quickstart
Docs and examples require no login. Developer API calls require an account and API key. The consumer search connector works without either. Accounts start with 50 destination search calls, 50 room calls and 1,000 hotel information units, issued once. Billing and limits.