> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/13.-ai-integration-and-intelligent-systems/13.4-ai-integration-workflow-for-developers.md).

# 13.4 AI Integration Workflow for Developers

From a developer perspective, integrating AI into an application involves a structured workflow.

The process begins with identifying the data inputs required for the application. These inputs may include blockchain data, energy metrics, or user activity. The data is then processed through an AI system, which generates outputs such as predictions, classifications, or optimization parameters.

These outputs are then submitted to the blockchain through transactions or oracle mechanisms, allowing smart contracts to consume and act upon them.

This workflow ensures that AI remains an off-chain computation layer, while the blockchain serves as the source of truth for execution and state changes.


---

# 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.frequencychain.org/13.-ai-integration-and-intelligent-systems/13.4-ai-integration-workflow-for-developers.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.