> 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/content.md).

# Content

The RateGain **Hotel Content Database (HCD)** is a comprehensive database containing descriptive property information and image links, used to facilitate hotel reservations.  It supports the distribution of this data to RateGain **Alternate Distribution Systems (ADS)** partners and **Global Distribution Systems (GDS)** environments.

**HCD data** can be accessed and updated by suppliers via the **Content Manager GUI Interface (CMGUI)** and **HCD XML Update Interface.** These tools enable the supplier to create new property records or update existing property records. The HCD XML Update Interface utilizes the **Open Travel Alliance (OTA)** Hotel Descriptive Content Notif (HDCN) message structures and codes list, via an inbound web service.

RateGain offers two methods for the distribution of HCD content:

**1) Content Retrieval**: Allows online distribution partners to retrieve and locally store property information for faster access and improved performance. This method utilizes the Open Travel Alliance Hotel Descriptive Info (HDI) message structures, via a web service.

**2) Content Update**: Content updates are generated in real-time to GDSs and participating online distribution partners, whenever a supplier successfully updates a property in HCD. This method utilizes the Open Travel Alliance Hotel Descriptive Content Notif (HDCN) message structures, via an outbound web service.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.rategain.com/content.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.