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

# Integration guides

How to put PredictHQ into production.

Start with the [Standard integration pattern](/integrations/integration-guides/standard-integration-pattern.md) - the reference architecture for forecasting and decision systems, from location setup through features, events, and explainability. Grounding AI systems inside your environment extends the same architecture: see [Provisioned grounding](/integrations/integration-guides/provisioned-grounding.md). [Keep data updated via API](/integrations/integration-guides/keep-data-updated-via-api.md) and [Loading event data into a data warehouse](/integrations/integration-guides/loading-event-data-into-a-data-warehouse.md) cover the do-it-yourself path when managed delivery isn't an option, and [Integrate with Loop Links](/integrations/integration-guides/integrate-with-loop-links.md) lets frontline teams feed event corrections back into the data.

For which path to build at all, see [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 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/integrations/integration-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.