> 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](/getting-started/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/integrations/integration-guides.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.