---
name: foryou-hotel-price-watch
description: Find the current rate range for a hotel stay, compare total cost across sites, and tell the user whether to book now or wait.
permissions: [web.read]
publisher_did: did:web:for.you.com
---

# Hotel price watch

Find the current rate range for a hotel stay, compare total cost across sites, and tell the user whether to book now or wait.

## When to use

- "Is this a good price for a hotel in Paris?"
- "Find a cheaper hotel for my trip to Chicago"
- "Should I book my hotel now or wait?"

## Steps

1. Confirm the city or neighborhood, check-in and check-out dates, guests and rooms, and must-haves (parking, breakfast, a refundable rate).
2. Search current rates for those dates on two or three hotel-comparison sites and on the hotel's own site — direct and member rates are often lower.
3. Search typical rates for the same area and season so you can say whether today's price is low, normal, or high, and flag any big event in town that week.
4. Compare total cost, not the nightly rate: add resort fees, taxes, and parking, and note each option's free-cancellation deadline.
5. Recommend one path: book a refundable rate now and re-check before its cancellation deadline, or wait and re-check on a specific date. Suggest a reminder rather than claiming you will watch rates yourself.

## Stop and confirm with the user

- Before opening any booking or payment page on the user's behalf.
- Before choosing a non-refundable rate.
- Logins, card numbers, and security codes stay with the user: they type them into the provider's own site or app, never into this conversation.

## Looking things up

Use your own web search tool if you have one. If you call the You.com Search API
directly (https://api.you.com/v1/search), send both of these headers on every
request so it is attributed to this skill:

```
X-Client-Info: skill; client=foryou-hotel-price-watch/1.1.0; url=https://for.you.com/capabilities/hotel-price-watch
User-Agent: SKILL/(for.you.com hotel-price-watch)
```

Keep `skill` as the first X-Client-Info token and do not swap in your own client's
name. Neither header carries credentials; they are attribution only.

Prefer official and primary sources (government agencies, the company's own policy
pages) over forums and resellers, and tell the user which source each fact came from.