> 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/application-layer.md).

# Application Layer

The application layer serves as the primary interface for user interaction with the LazAI platform, designed to deliver coamprehensive lifecycle services spanning data processing, AI asset transactions, and management. By leveraging a diverse range of native decentralized applications (DApps) and robust tool integrations, the application layer not only provides advanced technical support for Web3 innovators but also ensures a seamless and user-friendly experience for Web2 participants. This enables developers, consumers, and data providers to efficiently integrate into the LazAI ecosystem, collectivelay driving the adoption and advancement of AI and blockchain technologies.

* **Alith - A Privacy-First AI Agent Framework:** Alith is a key functional component and development framework within the LazAI platform, enabling users to create and deploy personalized MicroAgents.
* **Agent Launchpad:** The Agent Launchpad enables developers and iDAO communities to create, customize, and launch AI agents as decentralized digital assets. 
* **DAT Marketplace:** The DAT Marketplace is LazAI’s primary trading and verification hub for AI assets, including datasets, AI models, and AI agents.
* **DeFAI:** The DeFAI module combines LazAI’s advanced AI technology with Web3’s decentralized finance (DeFi) capabilities to deliver innovative financial services.

Let's deep dive into each core component of application layer. 


---

# 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.lazai.network/application-layer.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.