> For the complete documentation index, see [llms.txt](https://docs.lazai.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lazai.network/platform-architecture/introduction.md).
# Introduction
LazAI is designed to create a fully decentralized AI ecosystem, enabling verifiable AI data, computation, and assetization. To achieve this, the platform follows a modular architecture that ensures seamless interaction between AI models, datasets, developers, and blockchain infrastructure.
The LazAI Platform Architecture consists of the following layers:
* **Application Layer:** By combining on-chain verification, decentralized computing, and tokenized AI asset management, the application layer establishes a robust Web3-native AI infrastructure
* **Trust and Execution Layer:** Powered by LazChain, this layer serves as the core infrastructure for AI asset issuance, circulation, and computation verification.
* **Extension Layer:** Facilitates external data integration, model provider participation, and advanced AI service expansion to enhance interoperability across Web3.
---
# 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.lazai.network/platform-architecture/introduction.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.