> 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/2.-architecture-overview/2.4-integration-with-protocol-layers.md).
# 2.4 Integration with Protocol Layers
The architecture is not isolated, it integrates directly with other layers of the FreCx ecosystem.
The Energy Data Layer feeds real-world data into the execution environment, enabling smart contracts to respond to external inputs. The AI layer analyzes network activity and optimizes performance, validator participation, and resource allocation.
These integrations ensure that FreCx operates not just as a blockchain, but as a multi-layer infrastructure system.
The FreCx architecture provides a foundation that balances performance, security, and extensibility. By structuring responsibilities across specialized node roles and integrating additional data and intelligence layers, the network enables developers to build applications that are both scalable and deeply connected to real-world systems.
---
# 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/2.-architecture-overview/2.4-integration-with-protocol-layers.md?ask=&goal=
```
`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.
