> 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/data-anchoring-token-dat/concepts-and-architecture/value-semantics.md). # Value Semantics #### 1. Service Usage (Agent Call Credit) Every DAT token includes a value field representing service credit. It can be used to: * Call Alith Agents * Pay for dataset/model usage * Be consumed per use, recharged, or reused **Example:** A DAT with CLASS = 0x03 and value = 1000 allows 1000 calls to a model or equivalent compute. Extensions: * Value can be recharged * Value is deducted upon use and recorded on-chain for traceability #### 2. Revenue Share (Fractional Ownership) In dataset or model-based DATs, value also indicates fractional ownership, allowing holders to earn revenue share: * If a model is used by other agents, income is split proportionally * If a dataset is used for training, contributors earn a share * Rewards are automatically settled to token holders — no manual claim needed **Example:** * Model DAT #1234 has 10,000 total shares * You hold a token with value = 500 * If the model earns 10,000 DAT in a month, you receive:\ 500 / 10,000 × 10,000 = 500 DAT --- # 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/data-anchoring-token-dat/concepts-and-architecture/value-semantics.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.