> For the complete documentation index, see [llms.txt](https://developer.rategain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.rategain.com/ultradirect/ultradirect-transaction-samples-and-usage/rate-rules.md). # Rate Rules This transaction set is used to request additional policy information for a specific rate and room type combination that is not included in the availability response. All hotel CRSs support this transaction, however, each CRS operates differently and may or may not include all optional fields. #### Example Rate rules request: ```xml ``` * This request should NOT be used to check availability. * There is a maximum of 1 PropertyInformation element (brand;pid) that can be included in each request. * Rate Rule requests are used if more detailed information on the rate is required or if rate change details are required and not returned in the EST response. * This request is mandatory for public/commissionable rates. #### Example Rate Rules response: ```xml ``` * All relevant textual policies will need to be displayed for public rates but may not be needed for negotiated rates. * Except TaxDetail information, most policy information returned in the Rate Rules response is unstructured free-form description rather than structured coded and formatted responses. * Confirm availability by running an enhanced shopping request using RequestedAccuracy=SourceOnly between rate rules and book reservations.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.rategain.com/ultradirect/ultradirect-transaction-samples-and-usage/rate-rules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.