> 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/lazai-workflow-and-runtime/dat-specifications-and-flow.md).
# DAT Specifications & Flow
LazAI’s Data Anchoring Token (DAT) is a semi-fungible token (SFT) standard designed for AI dataset anchoring, licensing, and AI model provenance tracking. This protocol introduces a multi-layered ownership model, ensuring composability, structured access control, and verifiable AI asset usage in a decentralized ecosystem.
LazAI’s Data Anchoring Token (DAT) protocol redefines AI dataset ownership, licensing, and provenance tracking by integrating semi-fungible tokenization, on-chain verification, and decentralized AI economy models.
* **AI-Composable Economy:** Enables dataset/model composability for seamless AI evolution.
* **Verifiable AI Assets:** Ensures trustless authentication through cryptographic proofs.
* **Privacy-Preserving AI Training:** Supports ZK-protected AI model development.
* **AI Data Exchange & Monetization:** Unlocks new AI business models, allowing transparent revenue sharing.
This AI-first SFT standard establishes a scalable, trustless AI asset ecosystem, distinct from previous tokenization models.
---
# 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/lazai-workflow-and-runtime/dat-specifications-and-flow.md?ask=&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.
