> For the complete documentation index, see [llms.txt](https://docs.predicthq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.predicthq.com/getting-started/guides/forecasts-api-guides.md).

# Forecasts API guides

Guides for the Forecasts API - event-driven demand forecasts without building or maintaining your own model. Beam runs automatically; you supply demand data and consume forecasts with explainability built in.

Recommended order:

1. [Getting started with Forecasts API](/getting-started/guides/forecasts-api-guides/getting-started.md) - the full train, forecast, retrain lifecycle
2. [Understanding forecast accuracy metrics](/getting-started/guides/forecasts-api-guides/understanding-forecast-accuracy-metrics.md) - reading MAPE and the baseline comparison, so the lift is measured on your own demand
3. [Troubleshooting guide for Forecasts API](/getting-started/guides/forecasts-api-guides/troubleshooting.md) - when results don't look right

The Forecasts API also runs well inside multi-model setups - as one candidate in a champion-challenger selection or an ensemble alongside your existing forecasts.


---

# 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://docs.predicthq.com/getting-started/guides/forecasts-api-guides.md?ask=<question>&goal=<endgoal>
```

`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.