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

# Core concepts

The ideas the rest of the docs build on. If you read nothing else before integrating, read these - most integration mistakes come from skipping them.

Recommended order:

1. [Event-driven demand](/getting-started/core-concepts/event-driven-demand.md) - why real-world events move demand, and the four challenges any integration has to solve
2. [What is Beam?](/getting-started/core-concepts/what-is-beam.md) - the relevancy engine that calibrates everything downstream
3. [What is the Features API?](/getting-started/core-concepts/what-is-the-features-api.md) - model-ready signals instead of raw event aggregation
4. [Which API should I use?](/getting-started/core-concepts/which-api-should-i-use.md) - the right tool per task, including grounding
5. [Data Leakage in Backtesting](/getting-started/core-concepts/data-leakage-in-backtesting.md) - why forward-looking features evaluate honestly

[Guide to protecting PredictHQ data](/getting-started/core-concepts/guide-to-protecting-predicthq-data.md) covers the obligations that come with using the data.

For the recommended path by job - training, grounding, managed forecasts, or demand analysis - start with [How to use PredictHQ](/how-to-use-predicthq.md).


---

# 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://docs.predicthq.com/getting-started/core-concepts.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.