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

# Beam guides

Working guides and notebooks for Beam, PredictHQ's relevancy engine. Run Beam before configuring features or building forecasts - the `analysis_id` it produces calibrates everything downstream.

Recommended order:

1. [Understanding demand variability and event contribution in Beam](/getting-started/guides/beam-guides/understanding-demand-variability-and-event-contribution-in-beam.md) - how to read what Beam tells you about your demand
2. [ML features by location notebook](https://github.com/predicthq/phq-data-science-docs/blob/master/demand-forecasting-with-events/identify-location-level-features-with-beam-api.ipynb) - from analysis to model-ready features, per location
3. [ML features by group notebook](https://github.com/predicthq/phq-data-science-docs/blob/master/demand-forecasting-with-events/identify-group-level-features-with-beam-api.ipynb) - one consistent feature set across many locations sharing a model
4. [Sample demand data](/getting-started/guides/beam-guides/sample-demand-data.md) - the demand data format Beam expects

New to Beam? Read [What is Beam?](/getting-started/core-concepts/what-is-beam.md) first.


---

# 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/beam-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.