> For the complete documentation index, see [llms.txt](https://doc.moost.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.moost.io/platform-manual/context-services/weather-forecast.md).

# Weather Forecast

The Weather Forecast service provides accurate and up-to-date weather information for a given location. It offers various meteorological data points, such as temperature, humidity, wind speed, precipitation, and more. 

With the Weather Forecast service we can leverage weather conditions to enhance the quality of recommendations.

## Types

The Weather Forecast generates events with the following  types. This information is available for all customers of the recommender platform which provide a ZIP for their buildings.

<table><thead><tr><th width="387">Type</th><th>Description</th></tr></thead><tbody><tr><td>EXPECTED_OUTSIDE_TEMPERATURE</td><td>The expected outside temperature on the location of a given building for the next calendar day in degrees celsius.</td></tr><tr><td>EXPECTED_OUTSIDE_TEMPERATURE_4DAYS</td><td>The expected outside temperature on the location of a given building in 4 days in degrees celsius.</td></tr></tbody></table>


---

# 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://doc.moost.io/platform-manual/context-services/weather-forecast.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.