# HotelUse agent setup

Set up HotelUse in this project. Read https://www.hoteluse.dev/llms.txt and https://www.hoteluse.dev/docs/quickstart.md, then use the linked endpoint references or https://www.hoteluse.dev/v1/openapi.json. Ask me to sign in at https://www.hoteluse.dev/#dashboard if needed and complete verification in the browser. Help me create and securely store an API key as HOTELUSE_API_KEY; never print or commit the secret. Search a destination using hotel-local stay dates (today or later) and explicit occupancy, currency and residency. Display each provider's full-stay price and preserve room IDs, rate plans, fees and cancellation terms. Inspect coverage, errors and usage; honor account rate limits. Reuse an Idempotency-Key for uncertain retries. Show me the result and actual billed units. No booking or payment action is part of this API.

## Entry points

- Quickstart: https://www.hoteluse.dev/docs/quickstart.md
- All endpoint references: https://www.hoteluse.dev/llms.txt
- Full text: https://www.hoteluse.dev/llms-full.txt
- OpenAPI: https://www.hoteluse.dev/v1/openapi.json
- Dashboard: https://www.hoteluse.dev/#dashboard
- MCP: https://www.hoteluse.dev/mcp (Streamable HTTP with bearer header)

Developer HTTP, authenticated MCP and the separate consumer connector at /mcp/search return provider booking links by default when supplied. Expedia, Booking.com and Agoda links include HotelUse affiliate tracking; a booking may earn a commission. Dates, guests, currency, device and supplier rate-plan tokens are preserved. All booking_url values first use a signed HotelUse /go/ URL, then redirect to the provider; links expire with the 10-minute quote. HotelUse does not make bookings or take payment for hotel stays. Signup units are issued once: 50 search, 50 room, 1,000 hotel information units. After those: $0.04/search call, $0.06/room call, $0.005/new hotel information version.