> For the complete documentation index, see [llms.txt](https://gitbook.mor.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.mor.org/tokenomics/mor-utility.md).

# MOR Utility

At the core of the Morpheus token economy is MOR, a fair-launched utility token that powers the network, facilitating value movement and free-market dynamics among end users, builders, smart agents, DeAi applications, compute providers, consumers, developers, and capital providers.

The utilities of the MOR token include:

* rewarding ecosystem contributors;
* the primary means of payment for ecosystem AI applications;
* providing access to services within the ecosystem;
* [Protocol-Owned Liquidity](/tokenomics/protocol-owned-liquidity-pol.md) asset;
* allowing MOR holders to stake tokens for a free daily compute quota, accessing the network’s entire compute capacity;
* a staking asset for Compute Providers competing for user inference requests;
* incentivizing participants in the capital providers’ [referral program](/tokenomics/referral-program.md);
* a base asset for projects launched with the [MOR-20 standard](/tokenomics/techno-capital-machine/mor-20-fair-launch-standard.md);
* a tool to allocate rewards to builders through staking;
* [locking MOR](/tokenomics/mor-emissions.md#tail-emissions) to ensure rewards distribution in future Epochs;
* a multichain asset that allows Morpheus to remain chain-agnostic, supporting interoperability across blockchain networks.

This list represents the foundational utility set of MOR, which continues expanding as the Morpheus ecosystem grows, bringing new functionalities and opportunities for MOR holders.


---

# 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://gitbook.mor.org/tokenomics/mor-utility.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.